This is the mail archive of the
mailing list for the Cygwin project.
Re: gcc 4.x for Cygwin?
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: Mailing List: CygWin-Apps <cygwin-apps at cygwin dot com>
- Date: Thu, 06 Dec 2007 00:39:32 -0500
- Subject: Re: gcc 4.x for Cygwin?
- References: <20071127173815.GA30894@calimero.vinschen.de> <20071129170838.GA24864@calimero.vinschen.de> <041b01c83686$3253f620$2e08a8c0@CAM.ARTIMI.COM>
Dave Korn wrote:
Option 2. I don't see there's any other sensible choice. Ultimately I
guess I'd like to figure out a way to make unwinding and exceptions interwork
with the native SEH to address the potential downside.
(1) There was supposed to be a Google Summer of Code project addressing
SEH in gcc. It was listed as an "accepted project" here:
But nothing seems to have actually happened, to judge by
(2) Curious: does using a -dw2 compiler work when linking against code
that was compiled using an sjlj compiler? e.g. in a static library or
in a shared library?
Or, because cygwin1.dll exposes a very C-ish (not C++-ish) interface,
then what about other C++ libraries, such as xerces or ncurses++?
If the answers to the questions above are "bad", then is the (official,
non-experimental) release of a gcc-4.x-dw2 compiler something that
should wait until cygwin-1.7, with all of the backward-incompatibility
he** implied by "bad" answers?
P.S. sorry for the delay in responding. I've been effectively offline
for several weeks (work+family).