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: Sun, 19 Apr 2015 21:37:00 -0000 [thread overview] Message-ID: <bug-65802-4-3ZNivWunCz@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 #5 from vries at gcc dot gnu.org --- Before the patch series, at 011.cfg we had this representation: ... ;; basic block 2, loop depth 0, count 0, freq 0, maybe hot ;; prev block 0, next block 3, flags: (NEW, REACHABLE) ;; pred: ENTRY (FALLTHRU) D.2342 = cD.2333.gp_offsetD.5; if (D.2342 >= 48) goto <bb 4>; else goto <bb 3>; ;; succ: 4 (TRUE_VALUE) ;; 3 (FALSE_VALUE) ;; basic block 3, loop depth 0, count 0, freq 0, maybe hot ;; prev block 2, next block 4, flags: (NEW, REACHABLE) ;; pred: 2 (FALSE_VALUE) D.2344 = cD.2333.reg_save_areaD.8; D.2345 = cD.2333.gp_offsetD.5; D.2346 = (sizetype) D.2345; addr.0D.2339 = D.2344 + D.2346; D.2347 = cD.2333.gp_offsetD.5; D.2348 = D.2347 + 8; cD.2333.gp_offsetD.5 = D.2348; goto <bb 5>; ;; succ: 5 (FALLTHRU) ;; basic block 4, loop depth 0, count 0, freq 0, maybe hot ;; prev block 3, next block 5, flags: (NEW, REACHABLE) ;; pred: 2 (TRUE_VALUE) D.2349 = cD.2333.overflow_arg_areaD.7; addr.0D.2339 = D.2349; D.2350 = D.2349 + 8; cD.2333.overflow_arg_areaD.7 = D.2350; ;; succ: 5 (FALLTHRU) ;; basic block 5, loop depth 0, count 0, freq 0, maybe hot ;; prev block 4, next block 6, flags: (NEW, REACHABLE) ;; pred: 3 (FALLTHRU) ;; 4 (FALLTHRU) d.1D.2351 = MEM[(intD.9 * * {ref-all})addr.0D.2339]; dD.2334 = d.1D.2351; eD.2335 = &dD.2334; __asm__("" : "=d" eD.2335); [LP 1] # USE = anything # CLB = anything m_fn1D.2327 (&aD.2330); ;; succ: 9 (EH) ;; 6 (FALLTHRU) ... There's no exception connected to the whole va_arg sequence. So the question is: should ifn_va_arg have ECF_NOTHROW?
next prev parent reply other threads:[~2015-04-19 21:37 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 [this message] 2015-04-20 7:23 ` vries at gcc dot gnu.org 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-3ZNivWunCz@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: linkBe 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).