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 c++/47478] [4.4 Regression] internal compiler error
Date: Thu, 27 Jan 2011 11:32:00 -0000 [thread overview]
Message-ID: <bug-47478-4-ugx871eHk6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47478-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47478
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |4.4.6
--- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-01-27 11:18:17 UTC ---
Looks somewhat familiar:
Program received signal SIGSEGV, Segmentation fault.
0x00000000007648d5 in cancel_loop_tree (loop=0xa5a5a5a5a5a5a5a5)
at /space/rguenther/src/svn/gcc-4_4-branch/gcc/cfgloop.c:1305
1305 while (loop->inner)
#0 0x00000000007648d5 in cancel_loop_tree (loop=0xa5a5a5a5a5a5a5a5)
at /space/rguenther/src/svn/gcc-4_4-branch/gcc/cfgloop.c:1305
#1 0x00000000007648d1 in cancel_loop_tree (loop=0x7fffeeaee7e0)
at /space/rguenther/src/svn/gcc-4_4-branch/gcc/cfgloop.c:1306
#2 0x00000000007677da in remove_path (e=0x7fffee3f2040)
at /space/rguenther/src/svn/gcc-4_4-branch/gcc/cfgloopmanip.c:353
#3 0x00000000009b7afe in peel_loop_completely (loop=0x7fffeeaee480)
at /space/rguenther/src/svn/gcc-4_4-branch/gcc/loop-unroll.c:506
#4 0x00000000009b73bd in peel_loops_completely (flags=2)
at /space/rguenther/src/svn/gcc-4_4-branch/gcc/loop-unroll.c:248
#5 0x00000000009b6aaf in unroll_and_peel_loops (flags=2)
at /space/rguenther/src/svn/gcc-4_4-branch/gcc/loop-unroll.c:157
#6 0x00000000009ac87e in rtl_unroll_and_peel_loops ()
Likely a dup of PR42229, fixed with
2009-12-02 Richard Guenther <rguenther@suse.de>
PR middle-end/42229
* cfgloopmanip.c (remove_path): Avoid cancelling loops twice.
next prev parent reply other threads:[~2011-01-27 11:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 17:49 [Bug c++/47478] New: " aleaverfay at gmail dot com
2011-01-26 17:52 ` [Bug c++/47478] " aleaverfay at gmail dot com
2011-01-26 19:11 ` aleaverfay at gmail dot com
2011-01-26 20:08 ` redi at gcc dot gnu.org
2011-01-26 21:24 ` [Bug c++/47478] [4.4/4.5 Regression] " hjl.tools at gmail dot com
2011-01-26 21:49 ` [Bug c++/47478] [4.4 " hjl.tools at gmail dot com
2011-01-27 2:09 ` hjl.tools at gmail dot com
2011-01-27 11:32 ` rguenth at gcc dot gnu.org [this message]
2011-01-29 17:35 ` [Bug rtl-optimization/47478] " mikpe at it dot uu.se
2011-04-16 10:32 ` jakub at gcc dot gnu.org
2012-03-13 17:19 ` jakub at gcc dot gnu.org
2014-02-16 13:17 ` jackie.rosen at hushmail dot com
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-47478-4-ugx871eHk6@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).