------- Comment #7 from hp at gcc dot gnu dot org 2009-01-21 22:00 ------- (In reply to comment #6) > However, I suspect that all the places that use may_trap_after_code_motion_p > in > fact expect it to have MTP_AFTER_MOVE | MTP_UNALIGNED_MEMS semantics as well.
Me too. > So I would propose to merge may_trap_or_fault_p and > may_trap_after_code_motion_p to one function (and replace the checks for > MTP_UNALIGNED_MEMS in may_trap_p_1 by MTP_AFTER_MOVE, as they IMHO handle > different instances of the same problem -- the code that does not fail at its > current location, but may fail elsewhere). Yes: I'll prepare a patch to replace (change back) calls to may_trap_after_code_motion_p with calls to may_trap_or_fault_p and fold MTP_AFTER_MOVE into MTP_UNALIGNED_MEMS. If the release managers deems that too invasive for 4.3 and 4.4, perhaps they can still agree with the patch in commen #3. Thanks for checking. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38921
