------- Comment #10 from ro at techfak dot uni-bielefeld dot de 2009-10-09
12:42 -------
Subject: Re: plugin-api.h unconditionally includes stdint.h
> ------- Comment #9 from espindola at google dot com 2009-10-08 18:20 -------
[...]
> The only thing the compiler should need the plugin-api.h for is the enum
> ld_plugin_symbol_resolution. If we split plugin-api.h in two, we would be able
> to compile gcc itself without stdint.h.
>
> The problem with this approach is that the lto plugin would still fail to
> build
> in a system without stdint.h. Is it OK to have optional features like the gold
> plugin not supported in systems like "Tru64 UNIX V4.0F"?
That would be no problem since AFAIK gold only supports ELF targets by
design, and Tru64 UNIX uses ECOFF. Not even GNU ld supports that anymore
(or the support has bitrotten to the point of being unusable).
> Yet another possibility would be to change the build system so that we always
> build the lto plugin with xgcc (in addition to the plugin-api.h split). No
> idea
> how hard this is.
Why all those contortions if there seems to be an easy way out: just use
the GCC_HEADER_STDINT macro from config/m4 and include the resulting (e.g.)
gstdint.h instead of stdint.h?
Rainer
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40790
