------- Comment #7 from sje at cup dot hp dot com 2008-10-16 21:32 ------- The new test that was added fails for me on ia64-*-* platforms too. It looks like the fix for the original bug is right in that it is preventing the volatile assignment in being moved but the test is bad because other instructions (not involving the volatile variable) are being moved out of the loop so the test does see the "Decided to move invariant" string in the loop dump file. The information in this file doesn't seem to be specific enough to allow for an easy way to check whether the assignment of g_361 specifically was or was not moved. If I compile with -O2 instead of -Os then I don't see any invariant code motion but I don't know if that is a way to fix the test or not since the original bug involved -Os.
-- sje at cup dot hp dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sje at cup dot hp dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35729