public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: optimization/10362: Optimization with constant shifts and com pares fails on MIPS
Date: Wed, 09 Apr 2003 23:16:00 -0000	[thread overview]
Message-ID: <20030409231600.17588.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/10362; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: Berger David-MGI2063 <dberger@motorola.com>
Cc: "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>,
   "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>
Subject: RE: optimization/10362: Optimization with constant shifts and com
 pares fails on MIPS
Date: Wed, 9 Apr 2003 18:07:54 -0500 (CDT)

 > volatile unsigned long i;
 > 
 > void test(void)
 > {
 >   i = (((i & 0xf0) >> 4) >= 14); /* This one generates incorrect code with -O2 */
 >   i = ((i & 0xf0) >= (14 << 4)); /* This is what the optimizer is trying to do */
 > }
 
 I think what the compiler actually does, is to transform it to 
   i = ((i & 0xf0) > (14<<4-1));
 However, since the lowest 4 bits of the left hand side of the comparison 
 are provably zero, this is equivalent to
   i = ((i & 0xf0) > (13<<4));
 
 Do you have a value for "i", where you actually get a wrong comparison?
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-04-09 23:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 23:16 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-09 23:16 Falk Hueffner
2003-04-09 23:06 Berger David-MGI2063
2003-04-09 23:06 Berger David-MGI2063

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=20030409231600.17588.qmail@sources.redhat.com \
    --to=bangerth@ices.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).