From: Michael Eager <eager@eagercon.com>
To: David Holsgrove <david.holsgrove@xilinx.com>
Cc: gcc-patches@gcc.gnu.org, John Williams <john.williams@xilinx.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Vinod Kathail <vinod.kathail@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
Nagaraju Mekala <nagaraju.mekala@xilinx.com>,
Tom Shui <tom.shui@xilinx.com>
Subject: Re: [Patch, microblaze]: Add microblaze*-*-elf target
Date: Thu, 24 Jan 2013 15:38:00 -0000 [thread overview]
Message-ID: <5101557B.7020608@eagercon.com> (raw)
In-Reply-To: <CAM=EW8bBdQf=0rMuRP550=gXH6SwiF+Q0aykcTJ6N_szB3woxw@mail.gmail.com>
On 01/23/2013 08:24 PM, David Holsgrove wrote:
> Hi Michael,
>
> On 24 January 2013 00:58, Michael Eager <eager@eagercon.com> wrote:
>> On 01/20/2013 09:42 PM, David Holsgrove wrote:
>>>
>>> gcc/Changelog
>>>
>>> 2013-01-21 Edgar E. Iglesias <edgar.iglesias@gmail.com>
>>>
>>> * config.gcc (microblaze*-*-elf): Add new target
>>>
>>> libgcc/Changelog
>>>
>>> 2013-01-21 Edgar E. Iglesias <edgar.iglesias@gmail.com>
>>>
>>> * config.host (microblaze*-*-elf): Add new target
>>>
>>
>> Hi David --
>>
>> This appears to be identical the existing microblaze*-*-* target.
>> Why is an -elf target needed?
>>
>
> Its slightly different, the config.gcc -elf target adds newlib-stdint.h to
> the tm_file, and in libgcc/config.host we extend the extra_parts by
> adding crtbeginS.o, crtendS.o crtbeginT.o.
>
> It was more to keep the original generic target distinct from the
> developments to microblaze-*elf.
The generic microblaze*-*-* target is currently used for --target=microblaze-xilinx-elf.
After adding a microblaze*-*-elf target, what targets would use
generic target? If there are no known configurations which would
match, there's little value in keeping a target which is never built.
I don't have any objection to renaming the target from microblaze*-*-*
to microblaze-*-*-elf.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2013-01-24 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 5:43 David Holsgrove
2013-01-23 14:58 ` Michael Eager
2013-01-24 4:25 ` David Holsgrove
2013-01-24 15:38 ` Michael Eager [this message]
2013-01-25 0:38 ` David Holsgrove
2013-01-26 16:41 ` 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=5101557B.7020608@eagercon.com \
--to=eager@eagercon.com \
--cc=david.holsgrove@xilinx.com \
--cc=edgar.iglesias@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=john.williams@xilinx.com \
--cc=nagaraju.mekala@xilinx.com \
--cc=tom.shui@xilinx.com \
--cc=vidhum@xilinx.com \
--cc=vinod.kathail@xilinx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).