public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/20442] [3.3/3.4/4.0 Regression] problem mixing C++ exceptions and setjmp/longjmp with SJLJ exceptions Date: Sat, 12 Mar 2005 18:00:00 -0000 [thread overview] Message-ID: <20050312180005.13911.qmail@sourceware.org> (raw) In-Reply-To: <20050312174211.20442.paulthomas2@wanadoo.fr> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-12 18:00 ------- Confirmed, this is happens on all target which use setjmp/longjmp exceptions. I forget if any of the primary/secondary targets still use sjlj exceptions but this is a regression from 2.95.3. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 Known to fail| |4.1.0 Known to work| |2.95.3 Last reconfirmed|0000-00-00 00:00:00 |2005-03-12 18:00:03 date| | Summary|problem mixing C++ |[3.3/3.4/4.0 Regression] |exceptions and |problem mixing C++ |setjmp/longjmp under Cygwin |exceptions and | |setjmp/longjmp with SJLJ | |exceptions Target Milestone|--- |3.4.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20442
next prev parent reply other threads:[~2005-03-12 18:00 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-12 17:42 [Bug c++/20442] New: problem mixing C++ exceptions and setjmp/longjmp under Cygwin paulthomas2 at wanadoo dot fr 2005-03-12 17:47 ` [Bug middle-end/20442] " pinskia at gcc dot gnu dot org 2005-03-12 18:00 ` pinskia at gcc dot gnu dot org [this message] 2005-03-24 18:47 ` [Bug middle-end/20442] [3.3/3.4/4.0 Regression] problem mixing C++ exceptions and setjmp/longjmp with SJLJ exceptions mmitchel at gcc dot gnu dot org 2005-03-24 22:34 ` rth at gcc dot gnu dot org 2005-03-25 5:27 ` paulthomas2 at wanadoo dot fr 2005-03-27 6:20 ` paulthomas2 at wanadoo dot fr 2005-03-27 6:23 ` paulthomas2 at wanadoo dot fr 2005-03-31 22:18 ` rth at gcc dot gnu dot org 2005-04-01 4:52 ` paulthomas2 at wanadoo dot fr
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=20050312180005.13911.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).