public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/11813] Make GCC not to assume that C functions can't throw.
Date: Tue, 05 Aug 2003 23:42:00 -0000 [thread overview]
Message-ID: <20030805234255.492.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030805225315.11813.v.haisman@sh.cvut.cz>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11813
bangerth at dealii dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Priority|P2 |P3
Last reconfirmed|0000-00-00 00:00:00 |2003-08-05 23:42:54
date| |
Target Milestone|3.4 |---
Version|3.3.1 |3.4
------- Additional Comments From bangerth at dealii dot org 2003-08-05 23:42 -------
I can confirm this. However, I personally think that if you want to make
this happen (i.e. want to propagate C++ exceptions through C code), then
you should have to pay the price of giving -fexceptions to the command
line.
next prev parent reply other threads:[~2003-08-05 23:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 22:53 [Bug c++/11813] New: " v dot haisman at sh dot cvut dot cz
2003-08-05 22:54 ` [Bug c++/11813] " v dot haisman at sh dot cvut dot cz
2003-08-05 22:55 ` v dot haisman at sh dot cvut dot cz
2003-08-05 22:55 ` v dot haisman at sh dot cvut dot cz
2003-08-05 22:56 ` v dot haisman at sh dot cvut dot cz
2003-08-05 23:16 ` [Bug other/11813] " pinskia at physics dot uc dot edu
2003-08-05 23:42 ` bangerth at dealii dot org [this message]
2003-08-06 7:29 ` gdr at integrable-solutions dot net
2003-08-06 7:33 ` gdr at integrable-solutions dot net
2005-01-25 16:13 ` [Bug c/11813] make -fexceptions default for c and objective-c 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=20030805234255.492.qmail@sources.redhat.com \
--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).