public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/28917]  New: try/catch block removed. too optimistic optimization?
Date: Thu, 31 Aug 2006 19:06:00 -0000	[thread overview]
Message-ID: <bug-28917-7667@http.gcc.gnu.org/bugzilla/> (raw)

with fixed PR26208 we can throw exceptions from signal handlers.
catch() works pretty fine with complex call-chain but fails on
simple testcase.

#include <csignal>
void signalHandler( int signalNumber )
{
        throw 0;
}
int main()
{
        signal( SIGSEGV, signalHandler );
        try
        {
                int* p = 0;
                *p = 0;
        }
        catch ( int )
        {
        }
        return 0;
}

$ g++ throw_from_sighandler.cpp -O1 --save-temps && ./a.out
terminate called after throwing an instance of 'int'
zsh: abort      ./a.out

main:
        subq    $8, %rsp
        movl    $_Z13signalHandleri, %esi
        movl    $11, %edi
        call    signal
        movl    $0, 0
        movl    $0, %eax
        addq    $8, %rsp
        ret


-- 
           Summary: try/catch block removed. too optimistic optimization?
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pluto at agmk dot net
GCC target triplet: x86-64-linux


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


             reply	other threads:[~2006-08-31 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-31 19:06 pluto at agmk dot net [this message]
2006-08-31 19:09 ` [Bug other/28917] " pinskia at gcc dot gnu dot org
2006-08-31 19:13 ` pluto at agmk dot net
2006-08-31 19:27 ` [Bug rtl-optimization/28917] " pinskia at gcc dot gnu dot 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-28917-7667@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).