------- Comment #6 from rakdver at gcc dot gnu dot org 2006-02-16 13:38 ------- Sadly, Jakub is probably right -- since the very beginning, MEM_NOTRAP_P was used to mean that the mem cannot trap in its current context. This makes MEM_NOTRAP_P completely useless as far as code motion is concerned (and I would be very surprised if there were not some other uses of may_trap_p that are wrong because of this).
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26316
