Fwd: Symbols in .comm doesn't move to .sbss?

Fwd: Symbols in .comm doesn't move to .sbss?

[Masaki Muranaka]

Hello all,

I sent same question to gdb-patches yesterday.
Let me send again since this issue is about gas, not gdb.

My first post is follows:
- - -
Gas on MIPS|Alpha targets, symbols in the common sections
should be moved to .sbss depends on its size.

I found a support in read.c / bss_alloc().
The symbol in .lcomm will be collected because bss_alloc
is called by s_lcomm. But there is no path for .comm.
So the symbols in .comm will be never moved to .sbss.

Is this a bug? or a correct behavior?
- - -

And replies at gdb-patches is follows:

> From: Masaki Muranaka <monaka@monami-software.com>
> Date: 2006年5月20日 20:14:58:JST
> To: gdb-patches@sourceware.org
> Cc: Andreas Schwab <schwab@suse.de>
> Subject: Re: Symbols in .comm doesn't move to .sbss?
>
>
> On 2006/05/20, at 16:53, Andreas Schwab wrote:
>>> Is this a bug? or a correct behavior?
>>
>> I don't think it would be correct to move .comm to .sbss, since  
>> the symbol
>> could be merged with a larger .comm symbol of the same name in a  
>> different
>> module during linking.
>
> Thanks for your opinion.
> Then, is it be correct to move .lcomm to .sbss?
> And it seems symbols in .comm was moved to .sbss
> when I use MIPS SDE. Is it SDE's bug?
>
> Still I'm a little bit confused...
>
>
> --
> Masaki Muranaka
> Monami software
>
>

--
Masaki Muranaka
Monami software

Re: Fwd: Symbols in .comm doesn't move to .sbss?

[Alan Modra]

On Sat, May 20, 2006 at 09:11:35PM +0900, Masaki Muranaka wrote:
> The symbol in .lcomm will be collected because bss_alloc
> is called by s_lcomm. But there is no path for .comm.
> So the symbols in .comm will be never moved to .sbss.

The linker can do this.  See add_symbol_hook in bfd/ source files.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre