public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65802] [6 Regression] ICE in redirect_eh_edge_1, at tree-eh.c:2335
Date: Mon, 20 Apr 2015 07:23:00 -0000 [thread overview]
Message-ID: <bug-65802-4-46wI9SWCQt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65802-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65802
--- Comment #6 from vries at gcc dot gnu.org ---
(In reply to vries from comment #5)
> So the question is: should ifn_va_arg have ECF_NOTHROW?
Adding ECF_NOTHROW to ifn_va_arg also fixes the ICE.
And at gimplify_va_arg_expr, the VA_ARG_EXPR tree is non-throwing:
...
(gdb) call debug_generic_expr (*expr_p )
VA_ARG_EXPR <c>
(gdb) call debug_tree (*expr_p )
<va_arg_expr 0x7ffff661e9a0
type <pointer_type 0x7ffff64c97e0
type <integer_type 0x7ffff64a7690 int public SI
size <integer_cst 0x7ffff64c50a8 constant 32>
unit size <integer_cst 0x7ffff64c50c0 constant 4>
align 32 symtab 0 alias set -1 canonical type 0x7ffff64a7690
precision 32 min <integer_cst 0x7ffff64c5060 -2147483648> max <integer_cst
0x7ffff64c5078 2147483647>
pointer_to_this <pointer_type 0x7ffff64c97e0>>
sizes-gimplified unsigned DI
size <integer_cst 0x7ffff64a3e58 constant 64>
unit size <integer_cst 0x7ffff64a3e70 constant 8>
align 64 symtab 0 alias set -1 canonical type 0x7ffff64c97e0
pointer_to_this <pointer_type 0x7ffff6622540>>
side-effects
arg 0 <var_decl 0x7ffff64b0c60 c
type <array_type 0x7ffff64ccbd0 __builtin_va_list type <record_type
0x7ffff64cc738 __va_list_tag>
sizes-gimplified BLK
size <integer_cst 0x7ffff64c5318 constant 192>
unit size <integer_cst 0x7ffff64c52e8 constant 24>
align 64 symtab 0 alias set -1 canonical type 0x7ffff64cc888 domain
<integer_type 0x7ffff64cc7e0>>
used tree_1 decl_5 BLK file test.cc line 13 col 25 size <integer_cst
0x7ffff64c5318 192> unit size <integer_cst 0x7ffff64c52e8 24>
align 64 context <function_decl 0x7ffff66240d8 fn1>>
test.cc:15:32>
(gdb) call tree_could_throw_p (*expr_p )
$1 = false
...
I'll bootstrap and reg-test this fix.
next prev parent reply other threads:[~2015-04-20 7:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-65802-4@http.gcc.gnu.org/bugzilla/>
2015-04-19 8:59 ` vries at gcc dot gnu.org
2015-04-19 17:42 ` vries at gcc dot gnu.org
2015-04-19 21:30 ` vries at gcc dot gnu.org
2015-04-19 21:37 ` vries at gcc dot gnu.org
2015-04-20 7:23 ` vries at gcc dot gnu.org [this message]
2015-04-20 8:24 ` rguenth at gcc dot gnu.org
2015-04-20 8:42 ` vries at gcc dot gnu.org
2015-04-21 8:43 ` vries at gcc dot gnu.org
2015-04-21 8:46 ` vries at gcc dot gnu.org
2015-04-24 14:19 ` vries 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-65802-4-46wI9SWCQt@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).