[Bug rtl-optimization/45235] const volatile read moved out of order

2011-12-14 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45235 Andrew Pinski changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[Bug rtl-optimization/45235] const volatile read moved out of order

2011-01-11 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45235 Richard Guenther changed: What|Removed |Added Known to work||4.6.0 --- Comment #8 from Richard Guen

[Bug rtl-optimization/45235] const volatile read moved out of order

2011-01-11 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45235 --- Comment #7 from Richard Guenther 2011-01-11 15:41:23 UTC --- Author: rguenth Date: Tue Jan 11 15:41:17 2011 New Revision: 168663 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168663 Log: 2011-01-11 Richard Guenther PR middle-

[Bug rtl-optimization/45235] const volatile read moved out of order

2010-12-31 Thread bigotp at acm dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45235 --- Comment #6 from Peter A. Bigot 2010-12-31 17:57:14 UTC --- I've been running with this since my last comment with no problems. Could this be integrated into as many of trunk, gcc-4_4-branch, and gcc-4_5-branch as possible, please? Thanks.

[Bug rtl-optimization/45235] const volatile read moved out of order

2010-08-11 Thread rguenth at gcc dot gnu dot org
--- Comment #5 from rguenth at gcc dot gnu dot org 2010-08-11 23:11 --- (In reply to comment #4) > I don't see that the const qualifier should be relevant: doesn't it simply > indicate that the code is not permitted to write through that lvalue? That's true which is why I think this bug

[Bug rtl-optimization/45235] const volatile read moved out of order

2010-08-11 Thread bigotp at acm dot org
--- Comment #4 from bigotp at acm dot org 2010-08-11 22:54 --- I don't see that the const qualifier should be relevant: doesn't it simply indicate that the code is not permitted to write through that lvalue? (FWIW, the real code uses a memory mapped address and the const qualifier was p

[Bug rtl-optimization/45235] const volatile read moved out of order

2010-08-11 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2010-08-11 21:41 --- Hmm, I don't think this is correct as const volatile is a bit weird. It means a read must happen but it does not say order compared to other volatile variables (or at least I think). -- http://gcc.gnu.org/bugzi

[Bug rtl-optimization/45235] const volatile read moved out of order

2010-08-09 Thread rguenth at gcc dot gnu dot org
--- Comment #2 from rguenth at gcc dot gnu dot org 2010-08-09 13:56 --- Probably easier to not set TREE_READONLY or MEM_READONY_P here. Index: gcc/emit-rtl.c === --- gcc/emit-rtl.c (revision 163030) +++ gcc/emit-rtl.c

[Bug rtl-optimization/45235] const volatile read moved out of order

2010-08-09 Thread bigotp at acm dot org
--- Comment #1 from bigotp at acm dot org 2010-08-09 11:57 --- Created an attachment (id=21441) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21441&action=view) fixes for assumption that readonly means constant The problem is caused by the same sort of test as was fixed in a diffe