public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55107] [4.7/4.8 Regression] GCC in an infinite loop in PRE
Date: Sun, 09 Dec 2012 02:56:00 -0000 [thread overview]
Message-ID: <bug-55107-4-ZridovNPI2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55107-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55107
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Known to work| |4.4.5
Keywords| |compile-time-hog
Last reconfirmed| |2012-12-09
Ever Confirmed|0 |1
Summary|GCC in an infinite loop at |[4.7/4.8 Regression] GCC in
|-O2 |an infinite loop in PRE
Target Milestone|--- |4.7.3
Known to fail| |4.7.0, 4.8.0
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-12-09 02:55:54 UTC ---
#0 0x0000000000bd02db in bmp_iter_set (bi=0x7fffffffda90,
bit_no=0x7fffffffdab4) at /home/apinski/src/gcc-fsf/local//gcc/gcc/bitmap.h:532
#1 0x0000000000bd305f in bitmap_set_replace_value (set=0x1970858, lookfor=29,
expr=0x197d9a8) at /home/apinski/src/gcc-fsf/local//gcc/gcc/tree-ssa-pre.c:862
#2 0x0000000000bd30e6 in bitmap_value_replace_in_set (set=0x1970858,
expr=0x197d9a8) at /home/apinski/src/gcc-fsf/local//gcc/gcc/tree-ssa-pre.c:889
#3 0x0000000000bda1dd in insert_aux (block=0x7ffff70223a8) at
/home/apinski/src/gcc-fsf/local//gcc/gcc/tree-ssa-pre.c:3639
#4 0x0000000000bda294 in insert_aux (block=0x7ffff6fe6d00) at
/home/apinski/src/gcc-fsf/local//gcc/gcc/tree-ssa-pre.c:3654
#5 0x0000000000bda294 in insert_aux (block=0x7ffff6fe6bc8) at
/home/apinski/src/gcc-fsf/local//gcc/gcc/tree-ssa-pre.c:3654
#6 0x0000000000bda294 in insert_aux (block=0x7ffff6fe6820) at
/home/apinski/src/gcc-fsf/local//gcc/gcc/tree-ssa-pre.c:3654
#7 0x0000000000bda294 in insert_aux (block=0x7ffff6fe62d8) at
/home/apinski/src/gcc-fsf/local//gcc/gcc/tree-ssa-pre.c:3654
#8 0x0000000000bda294 in insert_aux (block=0x7ffff6fe6270) at
/home/apinski/src/gcc-fsf/local//gcc/gcc/tree-ssa-pre.c:3654
#9 0x0000000000bda294 in insert_aux (block=0x7ffff6fe61a0) at
/home/apinski/src/gcc-fsf/local//gcc/gcc/tree-ssa-pre.c:3654
#10 0x0000000000bda372 in insert () at
/home/apinski/src/gcc-fsf/local//gcc/gcc/tree-ssa-pre.c:3677
#11 0x0000000000bdd70f in do_pre () at
/home/apinski/src/gcc-fsf/local//gcc/gcc/tree-ssa-pre.c:4729
>Note that the stack trace looks the same as in PR55011.
That stack trace is just where xgcc is saying the cc1 was executed from.
next prev parent reply other threads:[~2012-12-09 2:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 14:23 [Bug tree-optimization/55107] New: GCC in an infinite loop at -O2 antoine.balestrat at gmail dot com
2012-12-09 2:56 ` pinskia at gcc dot gnu.org [this message]
2012-12-10 9:51 ` [Bug tree-optimization/55107] [4.7/4.8 Regression] GCC in an infinite loop in PRE rguenth at gcc dot gnu.org
2012-12-10 12:14 ` rguenth at gcc dot gnu.org
2012-12-10 14:01 ` rguenth at gcc dot gnu.org
2012-12-10 14:01 ` [Bug tree-optimization/55107] [4.7 " rguenth at gcc dot gnu.org
2013-02-05 12:57 ` rguenth at gcc dot gnu.org
2013-02-05 12:58 ` 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-55107-4-ZridovNPI2@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).