bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/23567] much larger static binaries compared to a few months ago


From: nickc at redhat dot com
Subject: [Bug ld/23567] much larger static binaries compared to a few months ago
Date: Thu, 23 Aug 2018 08:03:09 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=23567

Nick Clifton <nickc at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nickc at redhat dot com

--- Comment #3 from Nick Clifton <nickc at redhat dot com> ---
(In reply to Felix von Leitner from comment #0)

Hi Felix,

> What happened?

It looks like notes might be partly responsible:

>  Section to Segment mapping:
>   Segment Sections...
>    00     .note.gnu.property 
>    01     .text 
>    02     .rodata .eh_frame_hdr .eh_frame 
>    03     .data .bss 
>    04     .note.gnu.property 
>    05     .tbss 
>    06     .eh_frame_hdr 

Presumably you do not want these .note.gnu.property sections, or their
segments.  (On the assumption that you do not mind if the loader does
not have access to the information in these notes).

I do not think that there is a command line option to prevent their
generation, (although it could be argued that there ought to be one).
Would it be possible for you to use a custom linker script ?  One that
explicitly discards these note sections ?


The other difference I noticed is that there are now separate segments
for the .text section vs the .rodata/.eh_frame/.eh_frame_hdr sections.
This is a deliberate security enhancement as it allows the data segment
to marked as non-executable.  But there is a linker command line option
to disable this feature: "-z noseparate-code".

I hope that this helps.

Cheers
  Nick

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]