From: Michael Eager <eager@eagerm.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB: Add microblaze-*-rtems*
Date: Tue, 15 May 2012 13:29:00 -0000 [thread overview]
Message-ID: <4FB25A1E.4090400@eagerm.com> (raw)
In-Reply-To: <4FA92012.7020905@oarcorp.com>
On 05/08/2012 06:30 AM, Joel Sherrill wrote:
> OK to apply?
>
> 2012-05-07 Joel Sherrill <joel.sherrill@oarcorp.com>
>
> * configure.tgt (microblaze*-*-rtems*): New target.
The problem with the patch is that the microblaze*-*-rtems* pattern
will never be tested, since all targets (including microblaze-gnu-rtems)
will be matched by microblaze*-*-*.
It would be better to have a separate case which matches
microblaze*-*-rtems* preceding the microblaze*-*-* case. Although
Mark's comment about this being a redundant definition of hard
metal target remains valid.
I'm skeptical that adding microblaze-*-rtems to the targets will
have any effect on people making target changes which impact
RTEMS, especially if they build with --target=microblaze-gnu-elf.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
prev parent reply other threads:[~2012-05-15 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 13:31 Joel Sherrill
2012-05-08 13:54 ` Mark Kettenis
2012-05-08 13:57 ` Joel Sherrill
2012-05-15 13:29 ` Michael Eager [this message]
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=4FB25A1E.4090400@eagerm.com \
--to=eager@eagerm.com \
--cc=gdb-patches@sourceware.org \
--cc=joel.sherrill@oarcorp.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