From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: gcc@gcc.gnu.org
Subject: Re: [buildrobot] microblaze-elf / microblaze-linux
Date: Tue, 26 Nov 2013 18:00:00 -0000 [thread overview]
Message-ID: <5294E12B.7080908@rtems.org> (raw)
In-Reply-To: <5294DC85.4030700@oarcorp.com>
On 11/26/2013 06:38 PM, Joel Sherrill wrote:
>> Is there something that microblaze-rtems exposes that is not already
>> covered by other microblaze or rtems targets that are already included?
>
> I believe it was on the microblaze where someone broke the
> libgcc pattern for rtems by changing the pattern from
> XXX*-*-* to XXX*-*-elf.
Correct. microblaze-rtems* is incomplete in libgcc.
I have a patch pending for gcc-4.8.x, but haven't yet tried with
gcc-4.9.x.
Ralf
next prev parent reply other threads:[~2013-11-26 18:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 12:35 Joel Sherrill
2013-11-26 14:51 ` Jan-Benedict Glaw
2013-11-26 15:21 ` Joern Rennecke
2013-11-26 15:28 ` Jan-Benedict Glaw
2013-11-26 16:03 ` Michael Eager
2013-11-26 16:52 ` Joseph S. Myers
2013-11-26 17:38 ` Joel Sherrill
2013-11-26 18:00 ` Ralf Corsepius [this message]
2013-11-26 18:54 ` Joel Sherrill
2013-11-26 19:50 ` Joern Rennecke
2013-11-26 19:54 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2013-11-26 3:20 [buildrobot] First results of running contrib/config-list.mk Jan-Benedict Glaw
2013-11-26 3:27 ` [buildrobot] microblaze-elf / microblaze-linux Jan-Benedict Glaw
2013-11-26 15:51 ` Michael Eager
2013-11-26 16:08 ` Jan-Benedict Glaw
2013-11-26 16:13 ` Michael Eager
2013-11-26 16:17 ` Jan-Benedict Glaw
2013-11-26 17:16 ` Michael Eager
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=5294E12B.7080908@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=gcc@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).