public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/64756] New: wrong code at -O3 on x86_64-linux-gnu (in 32-bit mode)
Date: Fri, 23 Jan 2015 22:16:00 -0000	[thread overview]
Message-ID: <bug-64756-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64756

            Bug ID: 64756
           Summary: wrong code at -O3 on x86_64-linux-gnu (in 32-bit mode)
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: su at cs dot ucdavis.edu

The current gcc trunk miscompiles the following code on x86_64-linux at -O3 in
the 32-bit mode (but not in 64-bit mode). 

This is a regression from 4.9.x. 

It is quite strange that the bug seems to be sensitive to the name of the
variable "tmp" --- changing the variable to "b" for example will mask it. 

$ gcc-trunk -v
Using built-in specs.
COLLECT_GCC=gcc-trunk
COLLECT_LTO_WRAPPER=/usr/local/gcc-trunk/libexec/gcc/x86_64-unknown-linux-gnu/5.0.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-trunk/configure --prefix=/usr/local/gcc-trunk
--enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
gcc version 5.0.0 20150122 (experimental) [trunk revision 220011] (GCC) 

$ 
$ gcc-trunk -m32 -O2 small.c; a.out
$ gcc-trunk -m64 -O3 small.c; a.out
$ gcc-4.9 -m32 -O3 small.c; a.out
$ 
$ gcc-trunk -m32 -O3 small.c 
$ ./a.out
Aborted (core dumped)
$ 


---------------------------------



int a, *tmp, **c = &tmp;
volatile int d;
static int *volatile *e = &tmp;
unsigned int f; 

static void
fn1 (int *p)
{
  int g;
  for (; f < 1; f++)
    for (g = 1; g >= 0; g--)
      {
    d || d;
    *c = p;

    if (tmp != &a)
      __builtin_abort (); 

    *e = 0;
      }
}

int
main ()
{
  fn1 (&a);
  return 0;
}


             reply	other threads:[~2015-01-23 22:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 22:16 su at cs dot ucdavis.edu [this message]
2015-01-31 16:45 ` [Bug rtl-optimization/64756] " mikpelinux at gmail dot com
2015-01-31 17:41 ` mikpelinux at gmail dot com
2015-02-01 13:16 ` [Bug rtl-optimization/64756] [5 Regression] " hjl.tools at gmail dot com
2015-02-02  8:47 ` rguenth at gcc dot gnu.org
2015-02-02 10:44 ` jakub at gcc dot gnu.org
2015-02-02 10:57 ` jakub at gcc dot gnu.org
2015-02-03 20:42 ` jakub at gcc dot gnu.org
2015-02-04  8:42 ` 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-64756-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).