Record command lines in objects built by clang |
|||
Issue descriptiongcc has a .note section recording how an object is built.
,
Dec 5 2016
The .note section does not say how the object was built; in only list info like this:
Displaying notes found at file offset 0x00000254 with length 0x00000020:
Owner Data size Description
GNU 0x00000010 NT_GNU_ABI_TAG (ABI version tag)
OS: Linux, ABI: 2.6.24
Displaying notes found at file offset 0x00000274 with length 0x00000024:
Owner Data size Description
GNU 0x00000014 NT_GNU_BUILD_ID (unique build ID bitstring)
Build ID: 6b572eaa73419420e462ff8778203218aba5edae
,
Dec 5 2016
pretty sure they meant the .comment and .GCC.command.line sections. they aren't notes in the traditional ELF sense.
,
Dec 6 2016
and, for the record, we could not use the .GCC.command.line section generated by GCC because it gets merged for all object files into the final executable. So, you don't know if one object file was using a particular option or ALL of them were using it. For us, it is probably better to look at what is generated in the debug info which will keep the information per object file. Clang does not currently support putting this information in the debug information.
,
Jun 21 2017
,
Aug 3 2017
Closing. Please reopen it if its not fixed. Thanks! |
|||
►
Sign in to add a comment |
|||
Comment 1 by llozano@chromium.org
, Dec 3 2016Status: Assigned (was: Untriaged)