[Bug other/51732] New: typo in man gcc: "runt-time check"
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51732 Bug #: 51732 Summary: typo in man gcc: "runt-time check" Classification: Unclassified Product: gcc Version: 4.6.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassig...@gcc.gnu.org ReportedBy: martinw...@gmail.com "man gcc" says: -mno-8bit-idiv On some processors, like Intel Atom, 8bit unsigned integer divide is much faster than 32bit/64bit integer divide. This option will generate a runt-time check. If both dividend and divisor are within range of 0 to 255, 8bit unsigned integer divide will be used instead of 32bit/64bit integer divide. Can we fix "runt-time"? This is new in gcc-4.6
[Bug other/51732] typo in man gcc: "runt-time check"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51732 --- Comment #2 from Martin Guy --- :D :D Reminds me of the first edition of a Gutenberg text for Shakespeare which, due to an unfortunate OCR mismatch which also passed the spelling check, had "He held the babe in his anus" for several years. (That should be "arms")
[Bug bootstrap/59770] [4.9 Regression] bootstrap failure for arm-linux-gnueabi targeting armv4t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59770 Martin Guy changed: What|Removed |Added CC||martinwguy at gmail dot com --- Comment #1 from Martin Guy --- Duplicate of #59595 which also fails on armv5t host-built-target
[Bug target/39501] -O -ffinite-math-only gets min(x,y) optimization wrong for soft-float on arm-*-gnueabi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39501 --- Comment #17 from Martin Guy 2010-12-03 14:46:28 UTC --- Sort of. The cause of the bug was never found, and the workaround is to disable an instruction. It might be worth trying enabling movsfcc in current GCC and re-running the tests, since the conditional execution stuff in the middle end was rewritten between 4.3 and 4.4 if I remember correctly, so the actual bug in the middle end may have gone away with that rewrite.