From: Masaki Muranaka <monaka@monami-software.com>
To: gdb-patches@sourceware.org
Cc: Andreas Schwab <schwab@suse.de>
Subject: Re: Symbols in .comm doesn't move to .sbss?
Date: Sat, 20 May 2006 12:22:00 -0000 [thread overview]
Message-ID: <51CDB903-40CE-48C1-89F0-DA2E4FFD57E4@monami-software.com> (raw)
In-Reply-To: <jeu07l6sk3.fsf@sykes.suse.de>
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
next prev parent reply other threads:[~2006-05-20 11:15 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
2006-05-20 12:22 ` Masaki Muranaka [this message]
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=51CDB903-40CE-48C1-89F0-DA2E4FFD57E4@monami-software.com \
--to=monaka@monami-software.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@suse.de \
/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