public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "regehr at cs dot utah.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/52286] wrong code bug
Date: Thu, 16 Feb 2012 18:52:00 -0000	[thread overview]
Message-ID: <bug-52286-4-35okM70fM2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52286-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52286

John Regehr <regehr at cs dot utah.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chenyang at cs dot utah.edu

--- Comment #1 from John Regehr <regehr at cs dot utah.edu> 2012-02-16 18:48:18 UTC ---
[regehr@gamow 1]$ current-gcc -O0 small.c ; ./a.out 
1
[regehr@gamow 1]$ current-gcc -O1 small.c ; ./a.out 
0
[regehr@gamow 1]$ current-gcc -v
Using built-in specs.
COLLECT_GCC=current-gcc
COLLECT_LTO_WRAPPER=/uusoc/exports/scratch/regehr/z/compiler-install/gcc-r184311-install/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.7.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../configure --with-libelf=/usr/local --enable-lto
--prefix=/home/regehr/z/compiler-install/gcc-r184311-install
--program-prefix=r184311- --enable-languages=c,c++
Thread model: posix
gcc version 4.7.0 20120216 (experimental) (GCC) 
[regehr@gamow 1]$ cat small.c
int printf ( const char *, ... );

int c,
  a,
  b;

int
fn1 ( void )
{
  return c < 0;
}

int
main (  )
{
  b = ( ~a | 0 >= 0 ) & 0x98685255F;
  printf ( "%d\n", ( ( b ) < 0 ) );
  return 0;
}


  reply	other threads:[~2012-02-16 18:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 18:49 [Bug c/52286] New: " regehr at cs dot utah.edu
2012-02-16 18:52 ` regehr at cs dot utah.edu [this message]
2012-02-16 18:54 ` [Bug c/52286] " regehr at cs dot utah.edu
2012-02-16 19:22 ` jakub at gcc dot gnu.org
2012-02-16 19:29 ` [Bug c/52286] [4.6/4.7 Regression] " jakub at gcc dot gnu.org
2012-02-17  4:50 ` [Bug tree-optimization/52286] " pinskia at gcc dot gnu.org
2012-02-17  4:53 ` pinskia at gcc dot gnu.org
2012-02-17  5:46 ` pinskia at gcc dot gnu.org
2012-02-17 10:46 ` jakub at gcc dot gnu.org
2012-02-17 11:37 ` jakub at gcc dot gnu.org
2012-02-20 12:02 ` rguenth at gcc dot gnu.org
2012-02-20 12:54 ` jakub at gcc dot gnu.org
2012-02-20 12:59 ` [Bug tree-optimization/52286] [4.6 " jakub at gcc dot gnu.org
2012-02-23 18:25 ` jakub at gcc dot gnu.org
2012-02-23 21:53 ` jakub at gcc dot gnu.org

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=bug-52286-4-35okM70fM2@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).