From: Richard Henderson <rth@redhat.com>
To: Ian Lance Taylor <ian@wasabisystems.com>
Cc: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>, gcc@gcc.gnu.org
Subject: Re: -fzero-initialized-in-bss again
Date: Fri, 30 Apr 2004 23:06:00 -0000 [thread overview]
Message-ID: <20040430213905.GA5637@redhat.com> (raw)
In-Reply-To: <m3smel2pux.fsf@gossamer.airs.com>
On Fri, Apr 30, 2004 at 04:05:42PM -0400, Ian Lance Taylor wrote:
> Can you or he express it in C terms?
I doubt it. Because...
> Is the problem that -fzero-initialized-in-bss is causing a zero
> initialized variable to become a common variable? A BSS variable
> should not be a common variable. That would be wrong.
... this is *not* the case in C or C++.
The only way a variable should *ever* wind up in COMMON is if DECL_COMMON
is set by the front end. Otherwise it should go in .bss or .data.
r~
next prev parent reply other threads:[~2004-04-30 21:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 21:46 Richard Kenner
2004-04-30 21:52 ` Ian Lance Taylor
2004-04-30 23:06 ` Richard Henderson [this message]
2004-05-01 14:54 ` Eric Botcazou
2004-05-01 17:46 ` Richard Henderson
2004-05-01 8:03 ` Eric Botcazou
-- strict thread matches above, loose matches on Subject: below --
2004-05-03 18:00 Richard Kenner
2004-05-03 21:29 ` Gabriel Dos Reis
2004-05-01 15:29 Richard Kenner
2004-05-01 16:18 ` Eric Botcazou
2004-05-01 18:13 ` Richard Henderson
2004-05-03 2:40 ` Ian Lance Taylor
2004-05-03 17:56 ` Geoff Keating
2004-05-01 12:13 Richard Kenner
2004-05-01 13:11 ` Eric Botcazou
[not found] <10404302228.AA06573@vlsi1.ultra.nyu.edu>
2004-05-01 8:20 ` Eric Botcazou
2004-04-30 22:22 Richard Kenner
2004-04-30 21:31 Eric Botcazou
2004-04-30 21:39 ` Ian Lance Taylor
[not found] ` <jmad0txhey.fsf@desire.geoffk.org>
2004-05-01 7:33 ` Eric Botcazou
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=20040430213905.GA5637@redhat.com \
--to=rth@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=ian@wasabisystems.com \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).