This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Re[2]: bss section not getting zero-initialised vars
- To: etienne dot lorrain at ibm dot net, gcc at gcc dot gnu dot org
- Subject: Re: Re[2]: bss section not getting zero-initialised vars
- From: Mike Stump <mrs at windriver dot com>
- Date: Tue, 18 Jan 2000 08:29:56 -0800 (PST)
> Date: Tue, 18 Jan 2000 11:45:11 +0100 (CET)
> From: =?iso-8859-1?q?Etienne=20LORRAIN?= <etienne_lorrain@yahoo.fr>
> Reply-To: etienne.lorrain@ibm.net
> > > Looked at deja.com, found "-fconserve-space" on a
> > > 2 years + discussion on djgpp, it does not work here.
> >
> > Yes, it does work, you just are using the case where it works.
> I do not understand 100%: I am on Linux-i386 as I said, and retried
> yesterday; -fconserve-space or -fno-conserve-space does not change
> anything, are documented as obselete and only for C++.
I think we can punt this, I think there is more irrelevant
misunderstanding than anything else. Let me move out of the context
you introduced and just make some general remarks:
There are some platforms where -fconserve-space in fact does not and
cannot affect compilations. There are some platforms where
-fconserve-space does in fact affect compilations. -fconserve-space
is still in general a useful option to have in the compiler.
> Usually, I better like to keep variables (and structures) initialised
If the = 0 is removed, the variable is still initialized.