This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: 3.3 problem of -fzero-initialized-in-bss w/-ffreestanding
- From: Richard Henderson <rth at redhat dot com>
- To: Geoff Keating <geoffk at geoffk dot org>
- Cc: obrien at FreeBSD dot org, "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, gcc at gcc dot gnu dot org
- Date: Tue, 15 Jul 2003 16:13:02 -0700
- Subject: Re: 3.3 problem of -fzero-initialized-in-bss w/-ffreestanding
- References: <20030714173201.GB74108@dragon.nuxi.com> <jmwuekkf1b.fsf@desire.geoffk.org>
On Mon, Jul 14, 2003 at 01:51:44PM -0700, Geoff Keating wrote:
> > -no-zero-initialized-in-bss should be the default when -ffreestanding is
> > specified -- GCC should not^H^H^Hcannot make assumptions about when BSS
> > zeroing occurs in an -ffreestanding environment.
> >
> > Can this change be made for 3.3.1 release?
>
> Um, GCC already assumes that it happens before any code is run. When
> does your system do it?
Frankly, I agree. Zeroing of bss really ought to happen before you get
to C at all. Anything else will confuse even kernel programmers.
And if you can supply -ffrestanding, I think you can just as well
supply -fno-zero-initialized-in-bss at the same time.
In short, I don't think this is an appropriate change for any release,
much less 3.3.1.
r~