public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/46099] New: [4.5/4.6 Regression] ICE: in replace_ssa_name, at tree-cfg.c:5643 with -ftree-parallelize-loops -g
Date: Wed, 20 Oct 2010 16:42:00 -0000 [thread overview]
Message-ID: <bug-46099-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46099
Summary: [4.5/4.6 Regression] ICE: in replace_ssa_name, at
tree-cfg.c:5643 with -ftree-parallelize-loops -g
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: zsojka@seznam.cz
Created attachment 22096
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22096
reduced testcase
Compiler output:
$ gcc -ftree-parallelize-loops=2 -g -O pr46099.c
pr46099.c: In function 'foo':
pr46099.c:7:1: internal compiler error: in replace_ssa_name, at tree-cfg.c:5643
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Tested revisions:
r165719 - crash
r158095 - crash
r153685 - OK
4.5 r163761 - crash
4.4 r160770 - OK
next reply other threads:[~2010-10-20 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 16:42 zsojka at seznam dot cz [this message]
2010-10-20 17:58 ` [Bug tree-optimization/46099] " rguenth at gcc dot gnu.org
2010-10-20 20:37 ` hjl.tools at gmail dot com
2010-10-22 19:06 ` jakub at gcc dot gnu.org
2010-10-26 0:41 ` jakub at gcc dot gnu.org
2010-11-04 15:27 ` jakub at gcc dot gnu.org
2010-11-05 11:16 ` jakub at gcc dot gnu.org
2010-11-05 11:34 ` [Bug tree-optimization/46099] [4.5 " jakub at gcc dot gnu.org
2010-11-11 20:38 ` jakub at gcc dot gnu.org
2010-11-11 22:12 ` jakub at gcc dot gnu.org
2010-11-17 7:01 ` aoliva 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-46099-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).