------- Comment #3 from hp at gcc dot gnu dot org 2009-01-21 03:46 ------- Created an attachment (id=17156) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17156&action=view) Fix.
Looks like reorg.c wasn't to blame after all. Changes were made to may_trap_or_fault_p that made them stop considering (general, non-stack, non-const no special marks) MEMs as potentially trapping; instead putting that semantics into the new may_trap_after_code_motion_p but apparently without updating all callers. For may_trap_or_fault_p, the current only callers are resource.c (reorg.c's old friend) and ifcvt.c and both places assume the semantics in the patch. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38921
