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 middle-end/49189] [4.7 regression] infinite recursion in constant folder
Date: Fri, 27 May 2011 11:13:00 -0000 [thread overview]
Message-ID: <bug-49189-4-ASBBOZzvTo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49189-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49189
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2011.05.27 11:05:24
AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org
|gnu.org |
Target Milestone|--- |4.7.0
Ever Confirmed|0 |1
--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-05-27 11:05:24 UTC ---
Confirmed. Endlessly visiting
Breakpoint 6, fold_unary_loc (loc=0, code=TRUTH_NOT_EXPR, type=0x7ffff5b7e5e8,
op0=0x7ffff5b820a0) at /space/rguenther/src/svn/trunk/gcc/fold-const.c:7555
7555 enum tree_code_class kind = TREE_CODE_CLASS (code);
(gdb) call debug_generic_expr (op0)
(const boolean) ((boolean) ((system__unsigned_types__short_unsigned) v->OBJECT
>> (integer) i) & 1)
Breakpoint 6, fold_unary_loc (loc=0, code=NOP_EXPR, type=0x7ffff5b7e5e8,
op0=0x7ffff5b83000) at /space/rguenther/src/svn/trunk/gcc/fold-const.c:7555
7555 enum tree_code_class kind = TREE_CODE_CLASS (code);
(gdb) call debug_generic_expr (op0)
((boolean) ((system__unsigned_types__short_unsigned) v->OBJECT >> (integer) i)
& 1) == 0
(gdb) call debug_generic_expr (type)
const boolean
Breakpoint 7, fold_binary_loc (loc=0, code=EQ_EXPR, type=0x7ffff5b7e5e8,
op0=0x7ffff5b72e70, op1=0x7ffff7ee85e0)
at /space/rguenther/src/svn/trunk/gcc/fold-const.c:9280
9280 enum tree_code_class kind = TREE_CODE_CLASS (code);
(gdb) call debug_generic_expr (op0)
(boolean) ((system__unsigned_types__short_unsigned) v->OBJECT >> (integer) i) &
1
(gdb) call debug_generic_expr (op1)
0
Breakpoint 6, fold_unary_loc (loc=0, code=NOP_EXPR, type=0x7ffff5b7e5e8,
op0=0x7ffff5b72e70) at /space/rguenther/src/svn/trunk/gcc/fold-const.c:7555
7555 enum tree_code_class kind = TREE_CODE_CLASS (code);
(gdb) call debug_generic_expr (op0)
(boolean) ((system__unsigned_types__short_unsigned) v->OBJECT >> (integer) i) &
1
(gdb) call debug_generic_expr (type)
const boolean
Breakpoint 6, fold_unary_loc (loc=0, code=TRUTH_NOT_EXPR, type=0x7ffff5b7e5e8,
op0=0x7ffff5b820c8) at /space/rguenther/src/svn/trunk/gcc/fold-const.c:7555
7555 enum tree_code_class kind = TREE_CODE_CLASS (code);
...
next prev parent reply other threads:[~2011-05-27 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 10:57 [Bug middle-end/49189] New: " ebotcazou at gcc dot gnu.org
2011-05-27 10:59 ` [Bug middle-end/49189] " ebotcazou at gcc dot gnu.org
2011-05-27 11:13 ` rguenth at gcc dot gnu.org [this message]
2011-05-27 11:22 ` rguenth at gcc dot gnu.org
2011-05-27 11:59 ` rguenth at gcc dot gnu.org
2011-05-27 13:15 ` rguenth at gcc dot gnu.org
2011-05-27 13:16 ` rguenth at gcc dot gnu.org
2011-05-27 13:39 ` wschmidt 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-49189-4-ASBBOZzvTo@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).