This is the mail archive of the
mailing list for the GCC project.
Re: Skipping assembler when producing slim LTO files
- From: Ian Lance Taylor <ian at airs dot com>
- To: Richard Biener <richard dot guenther at gmail dot com>
- Cc: Jan Hubicka <hubicka at ucw dot cz>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Wed, 24 Sep 2014 05:40:51 -0700
- Subject: Re: Skipping assembler when producing slim LTO files
- Authentication-results: sourceware.org; auth=none
- References: <20140924054651 dot GB5371 at kam dot mff dot cuni dot cz> <CAFiYyc2=s7XCDoXZYAmMC1QckTxCxs23mzi5nYz8LTVvARM_vg at mail dot gmail dot com>
Richard Biener <email@example.com> writes:
> Btw, the patch is very hard to read as it moves (and modifies?) files
> at the same time. What's this magic "file attributes" we need?
The file attributes issue is the ELF machine number, class, OSABI,
flags, and endianness. When generating an ELF file it has to have this
information, and it has to match the objects generated by the assembler.
If it doesn't, the linker won't accept it and pass it to the plugin as
we require. We could of course build a large table of those numbers and
keep it updated for each target. But it's simpler to extract the
numbers from an existing object file that we know must be valid.