public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mlazar at kma dot zcu dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/27098] throw cause terminate() instead of catch Date: Mon, 10 Apr 2006 04:15:00 -0000 [thread overview] Message-ID: <20060410041522.22523.qmail@sourceware.org> (raw) In-Reply-To: <bug-27098-12503@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from mlazar at kma dot zcu dot cz 2006-04-10 04:15 ------- I observed that if the c source is compiled with "-foptimize-sibling-calls -O" options (on i686 in gcc 4.0.3), the exception is catched. So in this case, the terminate() function call: gcc -c helper.c g++ helper.o main.cc -o main and this case, the exception is catched: gcc -c helper.c -O -foptimize-sibling-calls g++ helper.o main.cc -o main -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27098
next prev parent reply other threads:[~2006-04-10 4:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-04-10 3:35 [Bug c++/27098] New: " mlazar at kma dot zcu dot cz 2006-04-10 3:37 ` [Bug c++/27098] " mlazar at kma dot zcu dot cz 2006-04-10 3:38 ` mlazar at kma dot zcu dot cz 2006-04-10 3:41 ` mlazar at kma dot zcu dot cz 2006-04-10 4:15 ` mlazar at kma dot zcu dot cz [this message] 2006-04-10 16:28 ` 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=20060410041522.22523.qmail@sourceware.org \ --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).