https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104911
--- Comment #5 from Iain Buclaw <ibuclaw at gdcproject dot org> --- (In reply to Rainer Orth from comment #4) > typesem.s indeed shows small codegen differences, while for semantic3.s > there are > both codegen differences per se as well as label renamings that may not > effect the > object files. With typesem.s, it looks like `byte.min' (-128) is being turned into 128 somewhere. Though I can't see how any change in the front-end would have caused that. With semantic3.s, it looks like the middle-end optimizer is removing some branches as dead code, when there should be no way it would possibly be able to infer that.
