This is the mail archive of the
mailing list for the binutils project.
Re: Map ".text.hot" and ".text.unlikely" input section prefixes to separate output sections.
- From: "shankarke at gmail dot com" <shankarke at gmail dot com>
- To: binutils at sourceware dot org
- Date: Fri, 16 Nov 2012 08:16:54 -0800 (PST)
- Subject: Re: Map ".text.hot" and ".text.unlikely" input section prefixes to separate output sections.
- References: <CAAs8HmygtSkVh3v4dz2hBTzS1AH-rLbBkTDJ-hVkzENC2sqQZg@mail.gmail.com>
Does the compiler generate .text.hot, .text.unlikely, and .text.startup
sections ? Or is this hand coded assembly ?
If its hand coded, why not use a linker script to do the same ?
Also why is gold mapping all .text.* sections to .text ? Doesnt it make
sense to merge all of them to sections of their own and when segments are
laid out, it can select how many of these sections are part of the segment.
While I am at this, Is there an ordering restriction of how segments should
appear in the output file ?
By ordering of segments, I mean that
segments with RX permissions appear before WX and so on, where does the code
handle ordering of segments in the gold linker ?
View this message in context: http://sourceware-org.1504.n7.nabble.com/Map-text-hot-and-text-unlikely-input-section-prefixes-to-separate-output-sections-tp136994p213373.html
Sent from the Sourceware - binutils list mailing list archive at Nabble.com.