public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brian at dessent dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/34684] Cross DLL Exceptions
Date: Wed, 09 Jan 2008 05:28:00 -0000	[thread overview]
Message-ID: <20080109031823.12549.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34684-15586@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from brian at dessent dot net  2008-01-09 03:18 -------
FSF gcc does not currently support exceptions across shared libraries on Cygwin
or MinGW.  This is because a shared libgcc is required, and libgcc only builds
static on those platforms.

For the 3.4 gcc releases that MinGW and Cygwin ship, there is a local patch
that lets exceptions across shared libraries work with static libgcc.  This
patch is quite a hack and was offered but never accepted upstream.  It cannot
be used with 4.x because the internals have changed so much.

The real solution is to build libgcc shared, which is what the MinGW gcc 4.2
release does with a number of MinGW-local patches.  They have not made their
way into FSF gcc, so until somebody works on this FSF gcc will continue to be
broken.


-- 


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


  parent reply	other threads:[~2008-01-09  3:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06  9:22 [Bug c++/34684] New: " XuHotdogs at gmail dot com
2008-01-06 15:27 ` [Bug target/34684] " pinskia at gcc dot gnu dot org
2008-01-06 18:14 ` XuHotdogs at gmail dot com
2008-01-09  5:28 ` brian at dessent dot net [this message]
     [not found] <bug-34684-4@http.gcc.gnu.org/bugzilla/>
2010-09-24 21:26 ` [Bug c++/34684] " ktietz 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=20080109031823.12549.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: 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).