From: Nicholas Nethercote <njn@cs.utexas.edu>
To: gcc@gcc.gnu.org
Subject: Where does the C standard describe overflow of signed integers?
Date: Mon, 11 Jul 2005 14:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0507110948081.20206@charco.cs.utexas.edu> (raw)
Hi,
There was recently a very long thread about the overflow behaviour of
signed integers in C. Apparently this is undefined according to the C
standard. I searched the standard on this matter, and while I did find
some paragraphs that described how unsigned integers must wrap around upon
overflow, I couldn't find anything explicit about signed integers. Can
someone point me to the relevant part(s) of the standard?
Also, does anyone know what the required behaviour for Fortran integers is
on overflow?
(I realise this isn't exactly on-topic for this list, but I thought it
reasonable to ask since this topic was discussed so enthusiastically
recently :)
Thanks very much.
Nick
next reply other threads:[~2005-07-11 14:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 14:58 Nicholas Nethercote [this message]
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
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=Pine.LNX.4.63.0507110948081.20206@charco.cs.utexas.edu \
--to=njn@cs.utexas.edu \
--cc=gcc@gcc.gnu.org \
/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).