c++/3099: cygwin: Many g++ EH failures

[Christopher Faylor]

On Wed, Jun 13, 2001 at 11:05:20AM +0100, Billinghurst, David (CRTS) wrote:
>I guessed this a couple of hours ago.  The testsuite results with
>--enable-sjlj-exceptions look OK.
>
>I would not know where to start with this, so I won't be updating anything
>in the short term.

If you can give me a clue about how to do this, I'll take a stab at it.

cgf

>> -----Original Message-----
>> From:	rth@gcc.gnu.org [SMTP:rth@gcc.gnu.org]
>> Sent:	Wednesday, June 13, 2001 4:21 PM
>> To:	Billinghurst, David (CRTS); 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
>> 
>> 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

-- 
cgf@cygnus.com                        Red Hat, Inc.
http://sources.redhat.com/            http://www.redhat.com/