From: "Dave Korn" <dave.korn@artimi.com>
To: "'Nathan Sidwell'" <nathan@codesourcery.com>,
"'Nicholas Nethercote'" <njn@cs.utexas.edu>
Cc: <gcc@gcc.gnu.org>
Subject: RE: Where does the C standard describe overflow of signed integers?
Date: Mon, 11 Jul 2005 15:23:00 -0000 [thread overview]
Message-ID: <SERRANOhKW2LwZlpPs50000048e@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <42D28CFF.6040208@codesourcery.com>
----Original Message----
>From: Nathan Sidwell
>Sent: 11 July 2005 16:15
> c99 6.5 para 5 (overflow is undefined)
Have I got an old draft or something, or is that the paragraph that begins
"If an _exceptional_ _condition_ occurs ..." ?
> I cannot find, in c99, a statement that all unsigned arithmetic obeys
> modulo laws -- only that integral conversions to them do.
Like I say, I'm not sure exactly what draft/version/spec I have here in
front of me, except that it says "ISO/IEC 9899:1999 (E)" at the top of each
page, but I've got a para 9 in 6.2.5 that says
" ... A computation involving unsigned operands can never overflow, because
a result that cannot be represented by the resulting unsigned integer type
is reduced modulo the number that is one greater than the largest value that
can be
represented by the resulting type."
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2005-07-11 15:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 14:58 Nicholas Nethercote
2005-07-11 15:07 ` Dave Korn
2005-07-11 16:07 ` Nicholas Nethercote
2005-07-11 17:04 ` Dave Korn
2005-07-11 15:15 ` Nathan Sidwell
2005-07-11 15:23 ` Dave Korn [this message]
2005-07-11 15:18 ` Overflow in Fortran (was: Where does the C standard describe overflow of signed integers?) Paul Brook
2005-07-12 23:13 ` Where does the C standard describe overflow of signed integers? Michael Meissner
2005-07-14 1:10 Paul Schlie
2005-07-14 1:59 ` Robert Dewar
2005-07-14 5:28 ` Paul Schlie
2005-07-14 17:57 ` Matthew Woodcraft
2005-07-14 18:36 ` Paul Koning
2005-07-14 19:09 Paul Schlie
2005-07-14 19:13 ` Robert Dewar
2005-07-14 19:28 ` Paul Schlie
2005-07-14 19:33 ` Robert Dewar
2005-07-14 20:13 ` Paul Schlie
2005-07-15 13:20 ` Georg Bauhaus
2005-07-15 13:33 ` Georg Bauhaus
2005-07-15 14:31 ` Dave Korn
2005-07-16 12:04 ` Georg Bauhaus
2005-07-16 14:26 ` Paul Schlie
2005-07-15 15:03 ` Paul Schlie
2005-07-16 12:12 ` Georg Bauhaus
2005-07-14 20:35 ` Paul Koning
2005-07-14 21:58 ` Paul Schlie
2005-07-15 7:04 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SERRANOhKW2LwZlpPs50000048e@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=gcc@gcc.gnu.org \
--cc=nathan@codesourcery.com \
--cc=njn@cs.utexas.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).