Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!ginosko!uunet!zephyr.ens.tek.com!orca!frip!andrew
From: andrew@frip.WV.TEK.COM (Andrew Klossner)
Newsgroups: gnu.gcc.bug
Subject: Re: GCC 1.35 'const' makes wrong assumptions about assembler
Message-ID: <4462@orca.WV.TEK.COM>
Date: 7 Sep 89 16:23:46 GMT
References: <956@kosman.UUCP>
Sender: nobody@orca.WV.TEK.COM
Organization: Tektronix, Wilsonville, Oregon
Lines: 11

Kevin O'Gorman (kevin@kosman.UUCP) reports that a "const" array
initialized to zero is translated to an assembly language "space"
pseudo-op in the text segment, and that the assembler allocates the
space but fills it with some non-zero value.

It's common for assemblers to satisfy a text "space" with no-op
instructions.  GCC should not assume that "space" in the text segment
will generate zeros.

  -=- Andrew Klossner   (uunet!tektronix!frip.WV.TEK!andrew)    [UUCP]
                        (andrew%frip.wv.tek.com@relay.cs.net)   [ARPA]