From: Andreas Schwab <schwab@suse.de>
To: Masaki Muranaka <monaka@monami-software.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Symbols in .comm doesn't move to .sbss?
Date: Sat, 20 May 2006 10:10:00 -0000 [thread overview]
Message-ID: <jeu07l6sk3.fsf@sykes.suse.de> (raw)
In-Reply-To: <63EE13CB-5DAC-43CD-8AC9-38009C20A7FF@monami-software.com> (Masaki Muranaka's message of "Sat, 20 May 2006 15:20:57 +0900")
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."
next prev parent reply other threads:[~2006-05-20 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 7:53 Masaki Muranaka
2006-05-20 10:10 ` Andreas Schwab [this message]
2006-05-20 12:22 ` Masaki Muranaka
2006-05-20 14:40 ` Masaki Muranaka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jeu07l6sk3.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=monaka@monami-software.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox