This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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);

> 	.data

> "__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
http://gcc.gnu.org/gcc-3.3/changes.html#3.3.3

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



    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]