Re: GCC 2.1 codegen bug when function is declared volatile

Article View: gnu.gcc.bug

Article #422

#422

From: Bruce_Martin
Date: Wed, 15 Apr 1992 16:21

19 lines
991 bytes

I reported:

> Gcc Version: 2.1
> Configuration: i386-mach
> Reported by: Bruce Martin (Bruce_Martin@NeXT.COM)
> 

> Description: if a function is declared volatile, gcc 2.1 produces
> completely bogus code when the optimizer is used.  I'm not at all
> sure what the correct response to the following C code should be,
> but the current behavior is definitely wrong (I'm assuming that
> the lack of any error messages means that the compiler should
> succeed in the compilation).


this is not a bug.  I mis-read the GCC documentation.  Sorry for the
false alarm.

				...bruce

Technical Details

Message-ID: <9204151621.AA03585@oz.NeXT.COM>

Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!next.com!Bruce_Martin

Show Full Headers

Complete Article Headers

Newsgroups: gnu.gcc.bug
Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!next.com!Bruce_Martin
From: Bruce_Martin@next.com
Subject: Re: GCC 2.1 codegen bug when function is declared volatile
Message-ID: <9204151621.AA03585@oz.NeXT.COM>
Sender: gnulists@ai.mit.edu
Organization: GNUs Not Usenet
Distribution: gnu
Date: Wed, 15 Apr 1992 16:21:30 GMT
Approved: bug-gcc@prep.ai.mit.edu
Lines: 20