On 01/23/2013 08:24 PM, David Holsgrove wrote:
Hi Michael,
On 24 January 2013 00:58, Michael Eager <ea...@eagercon.com> wrote:
On 01/20/2013 09:42 PM, David Holsgrove wrote:
gcc/Changelog
2013-01-21 Edgar E. Iglesias <edgar.igles...@gmail.com>
* config.gcc (microblaze*-*-elf): Add new target
libgcc/Changelog
2013-01-21 Edgar E. Iglesias <edgar.igles...@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 ea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
