From: corey taylor <corey.taylor@gmail.com>
To: John Yates <jyates@netezza.com>
Cc: Eljay Love-Jensen <eljay@adobe.com>,
Ulf Magnusson <ulfalizer@gmail.com>,
gcc-help@gcc.gnu.org
Subject: Re: Strange shifting behaviour
Date: Wed, 13 Jul 2005 19:01:00 -0000 [thread overview]
Message-ID: <2e393d0805071312011caf7d2c@mail.gmail.com> (raw)
In-Reply-To: <F0CD2E5262214F44959AD6AF34ADA66E01D13106@mail2.netezza.com>
> Are you going to issue a warning on every shift operation
> for which you cannot prove that the shift count is within
> the "defined behavior" range?
Well no, or you could and simply have it implement "up to" the defined
behavior range.
However, Ulf's example seems to show that a shift never happens
(although I'd like to see the code generated and cannot generate my
own at this time (hurricane issues had me take down gcc/g++ dev
machines). A more severe warning at least is called for here.
corey
next prev parent reply other threads:[~2005-07-13 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 18:47 John Yates
2005-07-13 19:00 ` Eljay Love-Jensen
2005-07-13 19:01 ` corey taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-13 18:10 John Yates
2005-07-13 18:20 ` corey taylor
2005-07-12 22:34 Ulf Magnusson
2005-07-12 22:44 ` Eljay Love-Jensen
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=2e393d0805071312011caf7d2c@mail.gmail.com \
--to=corey.taylor@gmail.com \
--cc=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jyates@netezza.com \
--cc=ulfalizer@gmail.com \
/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).