public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/51606] New: [4.7 Regression] FAIL: gcc.dg/vect/pr51015.c (internal compiler error) on ppc*-*-*
Date: Sat, 17 Dec 2011 23:49:00 -0000	[thread overview]
Message-ID: <bug-51606-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51606
           Summary: [4.7 Regression] FAIL: gcc.dg/vect/pr51015.c (internal
                    compiler error) on ppc*-*-*
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: dominiq@lps.ens.fr
                CC: iains@gcc.gnu.org, irar@gcc.gnu.org, jakub@redhat.com,
                    pthaugen@us.ibm.com
              Host: ppc*-*-*
            Target: ppc*-*-*
             Build: ppc*-*-*


Between revisions 182355 (OK, see
http://gcc.gnu.org/ml/gcc-testresults/2011-12/msg01667.html) and 182398 the
following tests have started to fail (see
http://gcc.gnu.org/ml/gcc-testresults/2011-12/msg01781.html )

FAIL: gcc.dg/vshift-1.c (internal compiler error)
FAIL: gcc.dg/vshift-1.c (test for excess errors)
WARNING: gcc.dg/vshift-1.c compilation failed to produce executable
FAIL: gcc.dg/vect/pr51015.c (internal compiler error)
FAIL: gcc.dg/vect/pr51015.c (test for excess errors)
FAIL: gcc.dg/vect/pr51015.c -flto (internal compiler error)
FAIL: gcc.dg/vect/pr51015.c -flto (test for excess errors)

AFAICT gcc.dg/vshift-1.c fails on powerpc-apple-darwin9 only.

The backtrace is

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x0000000c
flow_bb_inside_loop_p (loop=0x4288eb64, bb=0x0) at ../../work/gcc/cfgloop.c:776
776      source_loop = bb->loop_father;
(gdb) bt
#0  flow_bb_inside_loop_p (loop=0x4288eb64, bb=0x0) at
../../work/gcc/cfgloop.c:776
#1  0x00808d40 in vect_stmt_relevant_p (stmt=<value temporarily unavailable,
due to optimizations>, relevant=0xbfffd318, live_p=0xbfffd31c) at
../../work/gcc/tree-vect-stmts.c:260
#2  0x0080eae4 in vect_mark_stmts_to_be_vectorized (loop_vinfo=0x0) at
../../work/gcc/tree-vect-stmts.c:552
#3  0x00827260 in vect_analyze_loop (loop=0x993360) at
../../work/gcc/tree-vect-loop.c:1521
#4  0x008389b8 in vectorize_loops () at ../../work/gcc/tree-vectorizer.c:203
#5  0x005734d0 in execute_one_pass (pass=0x428d6144) at
../../work/gcc/passes.c:2079
#6  0x005738a8 in execute_pass_list (pass=0x428d6144) at
../../work/gcc/passes.c:2134
#7  execute_pass_list (pass=0xbb64c0) at ../../work/gcc/passes.c:2136
#8  execute_pass_list (pass=0xbb5d70) at ../../work/gcc/passes.c:2136
#9  0x006c85c8 in tree_rest_of_compilation (fndecl=0x428bbe00) at
../../work/gcc/tree-optimize.c:421
#10 0x00278e28 in cgraph_expand_function (node=0x428bbe00) at
../../work/gcc/cgraphunit.c:1818
#11 0x0027ae4c in cgraph_optimize () at ../../work/gcc/cgraphunit.c:1885
#12 0x0027b684 in cgraph_finalize_compilation_unit () at
../../work/gcc/cgraphunit.c:1327
#13 0x0001fdd4 in c_write_global_declarations () at
../../work/gcc/c-decl.c:10026
#14 0x00635cf4 in toplev_main (argc=3, argv=0x4288e6c0) at
../../work/gcc/toplev.c:573
#15 0x00001c34 in start ()


             reply	other threads:[~2011-12-17 23:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 23:49 dominiq at lps dot ens.fr [this message]
2011-12-18 12:02 ` [Bug tree-optimization/51606] " irar at il dot ibm.com
2011-12-19  9:18 ` jakub at gcc dot gnu.org
2011-12-19  9:24 ` jakub at gcc dot gnu.org
2011-12-19 14:23 ` 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-51606-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).