[Bug middle-end/45472] [4.5/4.6/4.7 Regression] ICE: in move_op_ascend, at sel-sched.c:6124 with -fselective-scheduling2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45472 --- Comment #18 from Andrey Belevantsev 2012-01-19 09:28:56 UTC --- (In reply to comment #17) > By the way I think we could get cases where the user wrote volatile in one > case > and non-volatile in another so fixing up the merging is still a good idea. Sure, but the comment 14 still applies -- I think that unless the middle-end will have the proper volatile semantics, it will be wrong to hide this issue in the scheduler, so I'm leaving this as it is for now.
[Bug middle-end/45472] [4.5/4.6/4.7 Regression] ICE: in move_op_ascend, at sel-sched.c:6124 with -fselective-scheduling2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45472 Andrew Pinski changed: What|Removed |Added Last reconfirmed|2010-09-01 03:03:31 |2011-12-09 --- Comment #17 from Andrew Pinski 2011-12-10 03:57:18 UTC --- By the way I think we could get cases where the user wrote volatile in one case and non-volatile in another so fixing up the merging is still a good idea.
[Bug middle-end/45472] [4.5/4.6/4.7 Regression] ICE: in move_op_ascend, at sel-sched.c:6124 with -fselective-scheduling2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45472 Richard Guenther changed: What|Removed |Added Target Milestone|4.5.3 |4.5.4 --- Comment #16 from Richard Guenther 2011-04-28 14:51:25 UTC --- GCC 4.5.3 is being released, adjusting target milestone.
[Bug middle-end/45472] [4.5/4.6/4.7 Regression] ICE: in move_op_ascend, at sel-sched.c:6124 with -fselective-scheduling2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45472 --- Comment #15 from Andrey Belevantsev 2011-04-08 06:42:22 UTC --- Just to remind the middle-end folks that stage 1 is a fine time for deciding on middle-end volatile semantics, before we forget about this for another 6 months :)
