From: Paul Schlie <schlie@comcast.net>
To: Georg Bauhaus <bauhaus@futureapps.de>, Dave Korn <dave.korn@artimi.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Where does the C standard describe overflow of signed integers?
Date: Sat, 16 Jul 2005 14:26:00 -0000 [thread overview]
Message-ID: <BEFE915C.AD94%schlie@comcast.net> (raw)
In-Reply-To: <42D8F7A3.2080400@futureapps.de>
> From: Georg Bauhaus <bauhaus@futureapps.de>
> 2) if putting local variables in registers becomes impossible
> there will be a significant cost. I wanted to get an impression
> of the cost. That's the reason for writing volatile in the
> declaration lines. Just for demo.)
I believe that was just a miss-statement, as I don't believe there's any
relationship between the two.
next prev parent reply other threads:[~2005-07-16 14:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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-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
2005-07-12 23:13 ` Michael Meissner
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=BEFE915C.AD94%schlie@comcast.net \
--to=schlie@comcast.net \
--cc=bauhaus@futureapps.de \
--cc=dave.korn@artimi.com \
--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).