This is the mail archive of the
mailing list for the GCC project.
- From: "Dave Korn" <dk at artimi dot com>
- To: <gcc at gcc dot gnu dot org>
- Date: Mon, 12 Jul 2004 12:32:10 +0100
- Subject: RE: bug?
> -----Original Message-----
> From: gcc-owner On Behalf Of Katsuya TANAKA
> Sent: 11 July 2004 15:58
> > grep ___malloc_top_pad mallocr.i
> unsigned long __malloc_top_pad = (0);
> "__malloc_top_pad" It goes into a data section.
> But gcc-3.3.4 and gcc-3.4.1 result is
> Why does it go into a BSS section?
It's a recent change in behaviour. From
"GCC 3.3.1 automatically places zero-initialized variables in the .bss
section on some operating systems. Versions of GNU Emacs up to (and
including) 21.3 will not work correctly when using this optimization; you
can use -fno-zero-initialized-in-bss to disable it. "
Can't think of a witty .sigline today....