From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Nick Clifton <nickc@cambridge.redhat.com>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] Include sh64 support for shle-*-netbsdelf*
Date: Mon, 13 May 2002 08:23:00 -0000 [thread overview]
Message-ID: <20020513082324.R3435@dr-evil.shagadelic.org> (raw)
In-Reply-To: <m3n0v4o2lh.fsf@north-pole.nickc.cambridge.redhat.com>; from nickc@cambridge.redhat.com on Mon, May 13, 2002 at 09:48:26AM +0100
On Mon, May 13, 2002 at 09:48:26AM +0100, Nick Clifton wrote:
> > + shle-*-netbsdelf*)
> > + targ_defvec=bfd_elf32_shlnbsd_vec
> > + targ_selvecs="bfd_elf32_shnbsd_vec shcoff_vec shlcoff_vec"
> > +#ifdef BFD64
> > + targ_selvecs="${targ_selvecs} bfd_elf32_sh64_vec bfd_elf32_sh64l_vec bfd_elf64_sh64_vec bfd_elf64_sh64l_vec"
> > +#endif
> > + ;;
> > sh*le-*-netbsdelf*)
> > targ_defvec=bfd_elf32_shlnbsd_vec
> > targ_selvecs="bfd_elf32_shnbsd_vec shcoff_vec shlcoff_vec"
>
> Doesn't the "sh*le-*-netbsdelf*" target (immediately below the lines
> you have added) already cover this situation ?
It appears as if the intent in other configurations was to include sh64
support only if the target was "sh", not "sh3" or "sh4", etc. Look down
one and two more, and you see the sh-*-netbsdelf* (added by hp when the
sh64 code went in) and the sh*-*-netbsdelf* (added by me when I checked
in NetBSD SH support) configs.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
next prev parent reply other threads:[~2002-05-13 15:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-11 11:56 Jason R Thorpe
2002-05-13 1:48 ` Nick Clifton
2002-05-13 8:23 ` Jason R Thorpe [this message]
2002-05-13 10:35 ` Nick Clifton
2002-05-13 15:13 ` Elena Zannoni
2002-05-13 14:28 ` Jason R Thorpe
2002-05-13 15:13 ` Elena Zannoni
2002-05-14 1:50 ` Nick Clifton
2002-05-14 6:51 ` Elena Zannoni
2002-05-14 7:27 ` Nick Clifton
2002-05-14 8:17 ` Elena Zannoni
[not found] ` <m3offha19r.fsf@north-pole.nickc.cambridge.redhat.com>
[not found] ` <3CE2B34F.EAAEF3F8@superh.com>
[not found] ` <15587.63152.235989.94659@localhost.redhat.com>
2002-05-17 5:40 ` print_insn_sh cleanup Joern Rennecke
2002-05-17 6:54 ` Elena Zannoni
2002-05-17 7:39 ` Joern Rennecke
2002-05-20 4:22 ` Alexandre Oliva
2002-05-20 6:29 ` Joern Rennecke
2002-05-20 6:57 ` Hans-Peter Nilsson
2002-05-14 8:20 ` [PATCH/RFA] Include sh64 support for shle-*-netbsdelf* Alexandre Oliva
2002-05-14 8:38 ` Elena Zannoni
2002-05-14 8:46 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020513082324.R3435@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickc@cambridge.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox