public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65177] New: [5 Regression]: extend jump thread for finite state automata causes miscompilation
Date: Mon, 23 Feb 2015 15:49:00 -0000	[thread overview]
Message-ID: <bug-65177-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 65177
           Summary: [5 Regression]: extend jump thread for finite state
                    automata causes miscompilation
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: spop at gcc dot gnu.org

Hello.

Starting with r218451, http://hmmer.janelia.org/ started to be miscompiled.

Steps to reproduce:
wget
http://selab.janelia.org/software/hmmer3/3.1b1/hmmer-3.1b1-linux-intel-x86_64.tar.gz
tar xvzf hmmer-3.1b1-cygwin.tar.gz 
cd hmmer-3.1b1-cygwin
CFLAGS="-g -O1 -ftree-vrp -fexpensive-optimizations" ./configure
make
make check

and following test fails:
gdb src/impl_sse/optacc_utest 

Program received signal SIGSEGV, Segmentation fault.
0x0000000000406a2c in select_i (k=<optimized out>, i=0, gx=0x45ed60,
gm=0x470420) at generic_optacc.c:293
293      path[0] = TSCDELTA(p7P_MI, k) * MMX(i-1,k);
(gdb) bt
#0  0x0000000000406a2c in select_i (k=<optimized out>, i=0, gx=0x45ed60,
gm=0x470420) at generic_optacc.c:293
#1  p7_GOATrace (gm=0x470420, pp=pp@entry=0x466150, gx=gx@entry=0x45ed60,
tr=tr@entry=0x46e4e0) at generic_optacc.c:220
#2  0x000000000040322f in utest_optacc (go=go@entry=0x44e010,
r=r@entry=0x44e170, abc=abc@entry=0x44eb50, bg=bg@entry=0x44ed90, M=M@entry=45,
L=L@entry=50, N=19) at ./optacc.c:659
#3  0x0000000000403613 in main (argc=<optimized out>, argv=<optimized out>) at
./optacc.c:801

I really tried to reduce test case, but unfortunately it's very hard to do it
for the project.
Please tell me if you are capable of reproducing the issue?

Thanks,
Martin


             reply	other threads:[~2015-02-23 15:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 15:49 marxin at gcc dot gnu.org [this message]
2015-02-23 15:58 ` [Bug tree-optimization/65177] " rguenth at gcc dot gnu.org
2015-02-23 16:19 ` trippels at gcc dot gnu.org
2015-02-23 17:41 ` marxin at gcc dot gnu.org
2015-02-23 17:48 ` spop at gcc dot gnu.org
2015-02-23 17:49 ` spop at gcc dot gnu.org
2015-02-25 21:33 ` mpolacek at gcc dot gnu.org
2015-02-25 23:05 ` spop at gcc dot gnu.org
2015-03-09 14:26 ` jakub at gcc dot gnu.org
2015-03-10 22:08 ` law at redhat dot com
2015-03-10 22:39 ` spop at gcc dot gnu.org
2015-03-10 22:42 ` spop at gcc dot gnu.org
2015-03-10 22:49 ` law at redhat dot com
2015-03-10 22:57 ` spop at gcc dot gnu.org
2015-03-10 23:03 ` law at redhat dot com
2015-03-11 16:27 ` spop at gcc dot gnu.org
2015-03-11 21:45 ` law at redhat dot com
2015-03-13 20:47 ` spop at gcc dot gnu.org
2015-03-13 21:05 ` spop at gcc dot gnu.org
2015-03-16 21:35 ` spop at gcc dot gnu.org
2015-03-17 19:05 ` law at redhat dot com
2015-03-17 20:15 ` spop at gcc dot gnu.org
2015-03-24 13:47 ` law at redhat dot com
2015-03-24 16:49 ` spop at gcc dot gnu.org
2015-03-25 23:26 ` spop at gcc dot gnu.org
2015-03-25 23:43 ` spop at gcc dot gnu.org
2015-10-28  9:01 ` yroux 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-65177-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).