On 09/27/2017 03:11 PM, Chris Adams wrote:
Once upon a time, Jan Kurik <jkurik@xxxxxxxxxx> said:
This change causes extra information to be stored in binary files
compiled by gcc. This information can be used by scripts to check on
various features of the file, such as the hardening options used of
potential ABI conflicts.
One thing that is not mentioned: how much information is stored in the
binaries? How much larger will the resulting binaries be?
Nick should be able to provide some statistics. It's designed to be
very small.
Would it be possible to include this in the debuginfo, rather than the
binaries?
Debuginfo packages are only available for bulk download after a compose.
They are not available for the buildroots. This makes it more
difficult to see, in a timely fashion, if changes to the build process
have the intended effect.
Thanks,
Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
