This is the mail archive of the 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: Some extensions to the .section directive for ELF and COFF

On Fri, Mar 27, 2015 at 08:48:32AM -0400, Rafael Espíndola wrote:
> The use case in mind is saving size during -ffunction-section,
> -fdata-section, so we need real sections, not subsections.

You said you wanted multiple .text sections with the same group
signature, or at least that's what I understood.  Why?  If they are
part of the same group then surely a single .text is sufficient.

> Alan, why is section symbols a problem? We just produce multiple
> sections symbols.

They may not be any trouble at all, but some targets create a normal
symbol with the same name as the section (sorry, I wasn't being very
clear when I said section symbols).  Presumably the symbol is used in
expressions relative to the start of the section, but I guess if your
assembly doesn't use that symbol you won't have a problem.

> Would an unique id help with the other issues (not
> familiar with ARM and IA64).

I'm also not that familiar, but I know that some ARM directives create
unwind information, stored in .ARM.exidx and .ARM.extab sections.
The section names are modified if the directives are in or and the sections are made part of the group if the
directive was in a group .text section.  ie. the assembler knows about
linkonce and comdat group sections, and names emitted by gcc
-ffunction-sections.  If you're using some other naming scheme then
you might need to tweak code in the ARM and IA64 assemblers.

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]