Don't hoist volatile mems out of loops

Joern Rennecke amylaar@cygnus.co.uk
Wed Dec 8 11:05:00 GMT 1999


In article < Pine.LNX.4.10.9912081614350.4323-100000@balti.cygnus.co.uk > you wrote:
: I noticed this bug when I tried to prevent overoptimization of a loop
: by adding "volatile" to a global variable and found that the compiler
: ignored it.  That was with gcc-2.95.2.

There have been a number of changes since gcc-2.95.2.  Have you checked that
this has not been fixed with this patch?

Thu Nov 11 19:45:24 1999  Jim Wilson  <wilson@cygnus.com>

        * loop.c (invariant_p, case MEM): Put MEM_VOLATILE_P check back.



More information about the Gcc-patches mailing list