This is the mail archive of the
mailing list for the Cygwin project.
RE: gcc 4.x for Cygwin?
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin-apps at cygwin dot com>
- Date: Tue, 4 Dec 2007 14:58:57 -0000
- Subject: RE: gcc 4.x for Cygwin?
- References: <20071127173815.GA30894@calimero.vinschen.de> <20071129170838.GA24864@calimero.vinschen.de>
On 29 November 2007 17:09, Corinna Vinschen wrote:
> On Nov 27 18:38, Corinna Vinschen wrote:
>> Now for something completely different:
>> Did anything happen in the gcc 4.x world which would help us to get a
>> gcc 4.x for Cygwin at one point? Are some of the problems reported in
>> http://sourceware.org/ml/cygwin-apps/2006-05/msg00044.html fixed in the
>> As for Charles' options how to go on:
>>> (1) either you drop ada and java support, and we live with the
>>> ever-increasing brokenness that will accumulate in the sjlj code, or
>>> (2) you switch to dwarf2, we keep ada and java, but loose the callback
>>> stuff and break backward compatibility.
>>> (3) you release TWO entire SETS of compilers: an sjlj one with only
>>> C/C++/Fortran, and a "real" one with DWARF2 and the full compiler
>>> suite. This is a support nightmare; I recommend against.
>> I'd opt for option 2.
> Dave? Any opinion from the gcc maintainer?
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.
Can't think of a witty .sigline today....