public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66396] New: [6 regression] FAIL: gcc.dg/graphite/run-id-pr47593.c execution test
Date: Wed, 03 Jun 2015 11:27:00 -0000	[thread overview]
Message-ID: <bug-66396-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 66396
           Summary: [6 regression] FAIL: gcc.dg/graphite/run-id-pr47593.c
                    execution test
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: schwab@linux-m68k.org
                CC: amker at gcc dot gnu.org
            Blocks: 48052
  Target Milestone: ---
            Target: m68k-*-*

$ gcc/xgcc -Bgcc/ ../gcc/testsuite/gcc.dg/graphite/run-id-pr47593.c   -O2
-fgraphite-identity  -lm    -o ./run-id-pr47593.exe -g
$ ./run-id-pr47593.exe
Segmentation fault

Program received signal SIGSEGV, Segmentation fault.
0x800004e6 in bar () at ../gcc/testsuite/gcc.dg/graphite/run-id-pr47593.c:21
21        return ***(int ***)p;
(gdb) p p
$1 = 0xeffff594 "\200\r\266\b"
(gdb) p {int**}p
$2 = (int **) 0x800db608
(gdb) p *$
Cannot access memory at address 0x800db608
(gdb) i local
f = {p = 0x800db608, q = 0x0}
j = 4
p = 0xeffff5c4 "\200\r\266\b"
x = <synthetic pointer>
y = 0xeffff5c0
(gdb) disass
Dump of assembler code for function bar:
   0x800004d8 <+0>:     linkw %fp,#-12
   0x800004dc <+4>:     moveq #4,%d0
   0x800004de <+6>:     movel %d0,%fp@(-12)
   0x800004e2 <+10>:    moveal %fp@(-4),%a0
=> 0x800004e6 <+14>:    moveal %a0@,%a0
   0x800004e8 <+16>:    movel %a0@,%d0
   0x800004ea <+18>:    unlk %fp
   0x800004ec <+20>:    rts
End of assembler dump.

Before r224020:
(gdb) disass bar
Dump of assembler code for function bar:
   0x800004d8 <+0>:     linkw %fp,#-24
   0x800004dc <+4>:     moveq #1,%d0
   0x800004de <+6>:     unlk %fp
   0x800004e0 <+8>:     rts
End of assembler dump.


05032b10839cf0498c992c819bf2358e86c22bb0 is the first bad commit
commit 05032b10839cf0498c992c819bf2358e86c22bb0
Author: amker <amker@138bc75d-0d04-0410-961f-82ee72b054a4>
Date:   Tue Jun 2 10:19:18 2015 +0000

        PR tree-optimization/48052
...
    git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@224020
138bc75d-0d04-0410-961f-82ee72b054a4


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48052
[Bug 48052] loop not vectorized if index is "unsigned int"


             reply	other threads:[~2015-06-03 11:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 11:27 schwab@linux-m68k.org [this message]
2015-06-03 11:29 ` [Bug tree-optimization/66396] " schwab@linux-m68k.org
2015-06-03 12:11 ` rguenth at gcc dot gnu.org
2015-06-03 13:04 ` rguenth at gcc dot gnu.org
2015-06-04  4:13 ` amker at gcc dot gnu.org
2015-06-04  4:13 ` amker at gcc dot gnu.org
2015-06-04 11:15 ` rguenth at gcc dot gnu.org
2015-06-08 11:51 ` rguenth at gcc dot gnu.org
2015-06-08 12:18 ` rguenth at gcc dot gnu.org
2015-06-09  7:52 ` rguenth at gcc dot gnu.org
2015-06-09  8:22 ` 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-66396-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).