This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Map ".text.hot" and ".text.unlikely" input section prefixes to separate output sections.


On Fri, Nov 16, 2012 at 05:19:01PM -0800, Ian Lance Taylor wrote:
> On Wed, Nov 14, 2012 at 5:06 PM, Sriraman Tallam <tmsriram@google.com> wrote:
> >> Ideally gold should group all input sections with the same name

I strongly disagree.  Grouping sections with the same name is a bad
idea, unless the name gives you some infomation from the compiler (as
it does with .text.hot* et al).  The problem with grouping sections
with the same name is that with -ffunction-sections objects, you'll
potentially move functions away from their callers, losing cache
locality.  The canonical example is a number of object files with
static "setup" functions.  These will all have code in .text.setup,
but there is no good reason to group these sections.

-- 
Alan Modra
Australia Development Lab, IBM


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]