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/54886] New: [4.8 Regression] FAIL: gcc.dg/graphite/pr(42521|42771).c (internal compiler error) due to revision 192219
Date: Wed, 10 Oct 2012 12:13:00 -0000 [thread overview]
Message-ID: <bug-54886-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54886
Bug #: 54886
Summary: [4.8 Regression] FAIL:
gcc.dg/graphite/pr(42521|42771).c (internal compiler
error) due to revision 192219
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: dominiq@lps.ens.fr
CC: hubicka@gcc.gnu.org
After revision 192219, I get
FAIL: gcc.dg/graphite/pr42521.c (internal compiler error)
FAIL: gcc.dg/graphite/pr42521.c (test for excess errors)
FAIL: gcc.dg/graphite/pr42771.c (internal compiler error)
FAIL: gcc.dg/graphite/pr42771.c (test for excess errors)
and it is still present at revision 192288. The backtrace for
gcc.dg/graphite/pr42521.c is
foo
Analyzing compilation unit
Performing interprocedural optimizations
<*free_lang_data> <visibility> <early_local_cleanups> <*free_inline_summary>
<emutls> <whole-program> <profile_estimate> <cp> <inline> <pure-const>
<static-var>Assembling functions:
fooisl_ctx.c:158: isl_ctx freed, but some objects still reference it
Program received signal SIGABRT, Aborted.
0x00007fff829930b6 in __kill () from /usr/lib/libSystem.B.dylib
(gdb) bt
#0 0x00007fff829930b6 in __kill () from /usr/lib/libSystem.B.dylib
#1 0x00007fff82a339f6 in abort () from /usr/lib/libSystem.B.dylib
#2 0x0000000141487f10 in isl_ctx_free () from /opt/mp/lib/libisl.10.dylib
#3 0x00000001004d5d1f in graphite_transform_loops () at
../../work/gcc/graphite.c:299
#4 0x00000001007e545a in graphite_transforms () at
../../work/gcc/tree-ssa-loop.c:252
#5 0x00000001005efd41 in execute_one_pass (pass=<value optimized out>) at
../../work/gcc/passes.c:2320
#6 0x00000001005f01bd in execute_pass_list (pass=<value optimized out>) at
../../work/gcc/passes.c:2381
#7 0x00000001005f01cf in execute_pass_list (pass=<value optimized out>) at
../../work/gcc/passes.c:2382
#8 0x00000001005f01cf in execute_pass_list (pass=<value optimized out>) at
../../work/gcc/passes.c:2382
#9 0x00000001005f01cf in execute_pass_list (pass=<value optimized out>) at
../../work/gcc/passes.c:2382
#10 0x000000010030a50b in expand_function (node=<value optimized out>) at
../../work/gcc/cgraphunit.c:1601
#11 0x000000010030c50a in compile () at ../../work/gcc/cgraphunit.c:1705
#12 0x000000010030ccbf in finalize_compilation_unit () at
../../work/gcc/cgraphunit.c:2080
#13 0x0000000100025813 in c_write_global_declarations () at
../../work/gcc/c/c-decl.c:10118
#14 0x00000001006abe21 in compile_file () at ../../work/gcc/toplev.c:560
#15 0x00000001006adc5c in toplev_main (argc=<value optimized out>, argv=<value
optimized out>) at ../../work/gcc/toplev.c:1866
#16 0x0000000100009cc4 in start (pc=<value optimized out>, bases=0x0) at
../../../work/libgcc/unwind-dw2-fde.c:1055
next reply other threads:[~2012-10-10 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 12:13 dominiq at lps dot ens.fr [this message]
2012-10-10 12:21 ` [Bug tree-optimization/54886] " rguenth at gcc dot gnu.org
2012-10-12 18:23 ` dominiq at lps dot ens.fr
2012-10-12 20:04 ` howarth at nitro dot med.uc.edu
2012-10-12 20:11 ` dominiq at lps dot ens.fr
2012-12-07 12:02 ` rguenth at gcc dot gnu.org
2012-12-07 13:16 ` rguenth at gcc dot gnu.org
2012-12-07 13:17 ` 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-54886-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).