From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-44297-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 21012 invoked by alias); 20 May 2006 07:53:57 -0000
Received: (qmail 20961 invoked by uid 22791); 20 May 2006 07:53:57 -0000
X-Spam-Check-By: sourceware.org
Received: from mx2.suse.de (HELO mx2.suse.de) (195.135.220.15)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 20 May 2006 07:53:25 +0000
Received: from Relay1.suse.de (mail2.suse.de [195.135.221.8]) 	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) 	(No client certificate requested) 	by mx2.suse.de (Postfix) with ESMTP id 946791EBC1; 	Sat, 20 May 2006 09:53:21 +0200 (CEST)
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?
References: <63EE13CB-5DAC-43CD-8AC9-38009C20A7FF@monami-software.com>
X-Yow: Here we are in America...  when do we collect unemployment?
Date: Sat, 20 May 2006 10:10:00 -0000
In-Reply-To: <63EE13CB-5DAC-43CD-8AC9-38009C20A7FF@monami-software.com> 	(Masaki Muranaka's message of "Sat, 20 May 2006 15:20:57 +0900")
Message-ID: <jeu07l6sk3.fsf@sykes.suse.de>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2006-05/txt/msg00426.txt.bz2

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."