public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54886] [4.8 Regression] FAIL: gcc.dg/graphite/pr(42521|42771).c (internal compiler error) due to revision 192219
Date: Fri, 07 Dec 2012 12:02:00 -0000 [thread overview]
Message-ID: <bug-54886-4-LTNvIntY8W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54886-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54886
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org
|gnu.org |
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> 2012-12-07 12:01:45 UTC ---
fooisl_ctx.c:158: isl_ctx freed, but some objects still reference it
this probably means some other data structure leaks:
==6257== 23,443 (48 direct, 23,395 indirect) bytes in 1 blocks are definitely
lo
st in loss record 778 of 781
==6257== at 0x4C2B14B: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd6
4-linux.so)
==6257== by 0x509087D: isl_pw_aff_alloc_size (in
/usr/lib64/libisl.so.10.0.0)
==6257== by 0x5090D3E: ??? (in /usr/lib64/libisl.so.10.0.0)
==6257== by 0x10651E9: wrap(isl_pw_aff*, unsigned int)
(graphite-sese-to-poly
.c:721)
==6257== by 0x106572B: extract_affine(scop*, tree_node*, isl_space*)
(graphite-sese-to-poly.c:833)
==6257== by 0x1065E22: build_loop_iteration_domains(scop*, loop*, int,
isl_set*, isl_set**) (graphite-sese-to-poly.c:1018)
==6257== by 0x1066D69: build_scop_iteration_domain(scop*)
(graphite-sese-to-poly.c:1411)
==6257== by 0x106B641: build_poly_scop(scop*) (graphite-sese-to-poly.c:3193)
==6257== by 0x10526F3: graphite_transform_loops() (graphite.c:287)
==6257== by 0xBEFE74: graphite_transforms() (tree-ssa-loop.c:258)
==6257== by 0x9C3EBE: execute_one_pass(opt_pass*) (passes.c:2335)
==6257== by 0x9C40B2: execute_pass_list(opt_pass*) (passes.c:2383)
and some more. I have a patch for the testcases at least.
next prev parent reply other threads:[~2012-12-07 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 12:13 [Bug tree-optimization/54886] New: " dominiq at lps dot ens.fr
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 [this message]
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-LTNvIntY8W@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).