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

Andreas Schwab schwab@suse.de
Sat May 20 10:10:00 GMT 2006


Masaki Muranaka <monaka@monami-software.com> writes:

> 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?

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.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



More information about the Gdb-patches mailing list