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/52353] -ftrapv -fnon-call-exceptions does not work
Date: Thu, 23 Feb 2012 13:21:00 -0000	[thread overview]
Message-ID: <bug-52353-4-fZv4P7gVWp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52353-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52353

--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-02-23 13:05:30 UTC ---
Created attachment 26732
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26732
patch

Patch that fixes my issue and works until rtl_dce, which still removes the
call,
even though it throws internally

(call_insn/u 15 13 36 3 (set (reg:DI 0 ax)
        (call (mem:QI (symbol_ref:DI ("__addvdi3") [flags 0x41]) [0 S1 A8])
            (const_int 0 [0])))
/space/rguenther/src/svn/trunk/gcc/testsuite/gcc.dg/pr47086.c:11 636
{*call_value}
     (expr_list:REG_DEAD (reg:DI 5 di)
        (expr_list:REG_DEAD (reg:DI 4 si)
            (expr_list:REG_UNUSED (reg:DI 0 ax)
                (expr_list:REG_EH_REGION (const_int 1 [0x1])
                    (nil)))))
    (expr_list:REG_DEP_TRUE (use (reg:DI 4 si))
        (expr_list:REG_DEP_TRUE (use (reg:DI 5 di))
            (nil))))

;; Successors:  5 (ab,abcall,eh,loop_exit) 4 [100.0%]  (fallthru)
;; lr  out       3 [bx] 6 [bp] 7 [sp] 16 [argp] 20 [frame] 41 [r12]


  reply	other threads:[~2012-02-23 13:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 13:05 [Bug middle-end/52353] New: " rguenth at gcc dot gnu.org
2012-02-23 13:21 ` rguenth at gcc dot gnu.org [this message]
2012-03-05 13:09 ` [Bug middle-end/52353] " rguenth at gcc dot gnu.org
2012-03-05 13:10 ` 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-52353-4-fZv4P7gVWp@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).