This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> I do not understand why you think this should be a target rather than a > host module. LTO makes perfect sense for a cross compiler - the compiler, > linker and presumably plug-in run on the host, while the target may be > bare-metal with no OS and incapable of running any of them. I just got confused. The attached patch builds it on host. What is the correct way to build it only if lto is being built? config-lang.in has no host_libs. > The plug-in should also share the same logic for finding libelf that > gcc/configure.ac has - allowing for possible different names for the > libelf header, and, should a --with-libelf option be added in future as > per <http://gcc.gnu.org/ml/gcc/2007-09/msg00117.html>, honouring that. > Thus I recommend putting that logic in a shared macro in config/, and > making sure the C sources allow for the different header names. Will work on that. > -- > Joseph S. Myers > joseph@codesourcery.com > Cheers, -- Rafael Avila de Espindola Google Ireland Ltd. Gordon House Barrow Street Dublin 4 Ireland Registered in Dublin, Ireland Registration Number: 368047
Attachment:
symtab.patch.bz2
Description: BZip2 compressed data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |