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: Patch: Add c6x-uclinux support


On Wed, 30 Mar 2011, Bernd Schmidt wrote:

> > I'm generally concerned that I don't understand why there are three 
> > sections rather than two here.  Why isn't .bss being given this property 
> > and used in place of .scommon?
> 
> Because it contains symbols that aren't common?

# ".bss" is near (small) BSS, ".far" is far (normal) BSS, ".const" is
# far read-only data, ".rodata" is near read-only data.  ".neardata"
# is near (small) data, ".fardata" is (along with .data) far data.

(from elf32_tic6x_le.sh).  What is the far analogue of .scommon?  Your 
patch doesn't change this comment explaining the sections, and I see no 
sign of any existing .common section name support for any target, or any 
reason why no far analogue would be needed.

elf32-ppc.c:ppc_elf_add_symbol_hook sets SEC_IS_COMMON on .sbss.  .sbss 
for that target corresponds to .bss for C6X, as far as the linker scripts 
are concerned - what goes wrong with that correspondence to require 
another section (but only one other section, not two)?

-- 
Joseph S. Myers
joseph@codesourcery.com


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