Bug 51732 - typo in man gcc: "runt-time check"
Summary: typo in man gcc: "runt-time check"
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: other (show other bugs)
Version: 4.6.3
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-02 13:02 UTC by Martin Guy
Modified: 2017-04-19 13:08 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Guy 2012-01-02 13:02:34 UTC 
"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
Comment 1 Martin Liška 2017-04-19 11:23:17 UTC 
Fixed in 4.7.
Comment 2 Martin Guy 2017-04-19 12:42:13 UTC 
: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")
Comment 3 Martin Liška 2017-04-19 13:08:24 UTC 
(In reply to Martin Guy from comment #2)
> :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")

:D funny things can happen!