This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
RE: c++/3099: cygwin: Many g++ EH failures
- To: "'rth at gcc dot gnu dot org'" <rth at gcc dot gnu dot org>, cgf at redhat dot com, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
- Subject: RE: c++/3099: cygwin: Many g++ EH failures
- From: "Billinghurst, David (CRTS)" <David dot Billinghurst at riotinto dot com>
- Date: Wed, 13 Jun 2001 11:05:20 +0100
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.
> -----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