------- Comment #8 from rguenth at gcc dot gnu dot org 2007-05-23 11:17 ------- This particular case is indeed an optimization issue and __udivdi3 can be avoided by using volatile as stated and verified.
-- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32044