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 lto/61741] New: wrong code by LTO on x86_64-linux-gnu
Date: Tue, 08 Jul 2014 03:49:00 -0000	[thread overview]
Message-ID: <bug-61741-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 61741
           Summary: wrong code by LTO on x86_64-linux-gnu
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: su at cs dot ucdavis.edu

The current gcc trunk miscompiles the following code when using LTO on
x86_64-linux-gnu in both 32-bit and 64-bit modes. 

This also seems to affect 4.6.x -- 4.9.x: 
(1) the generated code hangs for 4.6.x -- 4.8.x; and
(2) the generated code produces wrong result for 4.9.x.

$ 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/4.10.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 4.10.0 20140707 (experimental) [trunk revision 212319] (GCC) 
$ 
$ gcc-trunk -O0 -c foo.c          
$ gcc-trunk -O0 -c main.c
$ gcc-trunk -Os main.o foo.o 
$ a.out
0
$ 
$ gcc-trunk -flto -O0 -c foo.c
$ gcc-trunk -flto -O0 -c main.c
$ gcc-trunk -flto -Os main.o foo.o
$ a.out
1
$ 
$ cat foo.c
extern int a, b; 

void
foo (void)
{
  char c = 0;
  for (; a; a--)
    for (; c >= 0; c++);
  if (!c)
    b = 1;
}
$ cat main.c
int printf (const char *, ...);

extern void foo (void); 

int a = 1, b;

int
main ()
{
  foo ();
  printf ("%d\n", b);
  return 0;
}
$


             reply	other threads:[~2014-07-08  3:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  3:49 su at cs dot ucdavis.edu [this message]
2014-07-08  5:18 ` [Bug lto/61741] " andi-gcc at firstfloor dot org
2014-07-08  5:36 ` su at cs dot ucdavis.edu
2014-07-08  9:19 ` rguenth at gcc dot gnu.org
2014-07-09 12:06 ` rguenth at gcc dot gnu.org
2014-07-09 17:15 ` [Bug c/61741] " rguenth at gcc dot gnu.org
2014-07-09 17:15 ` rguenth at gcc dot gnu.org
2014-07-10 12:21 ` [Bug c/61741] wrong code with -fno-strict-overflow rguenth at gcc dot gnu.org
2014-07-17  7:58 ` rguenth at gcc dot gnu.org
2014-07-17  7:58 ` rguenth 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-61741-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).