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/51023] New: likely integer wrong code bug
Date: Tue, 08 Nov 2011 05:54:00 -0000	[thread overview]
Message-ID: <bug-51023-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51023
           Summary: likely integer wrong code bug
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: regehr@cs.utah.edu


Seen on Ubuntu 10.04.3.  The "-O0" result is correct.

[regehr@gamow tmp049]$ current-gcc -O0 small.c  ; ./a.out 
0
[regehr@gamow tmp049]$ current-gcc -O1 small.c  ; ./a.out 
1
[regehr@gamow tmp049]$ current-gcc -v

Using built-in specs.
COLLECT_GCC=current-gcc
COLLECT_LTO_WRAPPER=/uusoc/exports/scratch/regehr/z/compiler-install/gcc-r181147-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-r181147-install
--program-prefix=r181147- --enable-languages=c,c++
Thread model: posix
gcc version 4.7.0 20111108 (experimental) (GCC) 

[regehr@gamow tmp049]$ cat small.c


int printf (const char *, ...);

struct {
  int f0;
} g_24;

short func_11 (int si1)
{
  return si1;
}

int main ()
{
  int l_141 = 0x4272A;
  g_24.f0 = func_11 (l_141) == l_141;
  printf ("%d\n", g_24.f0);
  return 0;
}


             reply	other threads:[~2011-11-08  5:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  5:54 regehr at cs dot utah.edu [this message]
2011-11-08  6:47 ` [Bug c/51023] " regehr at cs dot utah.edu
2011-11-08 10:26 ` [Bug rtl-optimization/51023] [4.7 Regression] " rguenth at gcc dot gnu.org
2011-11-08 23:15 ` jakub at gcc dot gnu.org
2011-11-09  9:42 ` jakub at gcc dot gnu.org
2011-11-10 16:02 ` jakub at gcc dot gnu.org
2011-11-10 17:29 ` 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-51023-4@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).