This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Symbols in .comm doesn't move to .sbss?
- From: Andreas Schwab <schwab at suse dot de>
- To: Masaki Muranaka <monaka at monami-software dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 20 May 2006 09:53:16 +0200
- Subject: Re: Symbols in .comm doesn't move to .sbss?
- References: <63EE13CB-5DAC-43CD-8AC9-38009C20A7FF@monami-software.com>
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."