From mboxrd@z Thu Jan  1 00:00:00 1970
From: rth@gcc.gnu.org
To: David.Billinghurst@riotinto.com, cgf@redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rth@gcc.gnu.org
Subject: Re: c++/3099: cygwin: Many g++ EH failures
Date: Tue, 12 Jun 2001 23:21:00 -0000
Message-id: <20010613062100.16216.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-06/msg00543.html
List-Id: <gcc-prs.sourceware.org>

Old Synopsis: cygwin:  Many g++ EH failures
New Synopsis: cygwin: Many g++ EH failures

Responsible-Changed-From-To: unassigned->rth
Responsible-Changed-By: rth
Responsible-Changed-When: Tue Jun 12 23:20:59 2001
Responsible-Changed-Why:
    I'll take it.
State-Changed-From-To: analyzed->feedback
State-Changed-By: rth
State-Changed-When: Tue Jun 12 23:20:59 2001
State-Changed-Why:
    The problem is that Cygwin was changed from sjlj EH to call-frame EH,
    but the Cygwin runtime was not updated to match, and does not register
    the .eh_frame data, so we rather quickly abort.
    
    From my point of view, the preferable option is to update the Cygwin
    runtime rather than drop back to sjlj, but I don't know if that's
    really an option for you.
    
    Please advise.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3099&database=gcc