This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/3099: cygwin: Many g++ EH failures
- To: David dot Billinghurst at riotinto dot com, 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, rth at gcc dot gnu dot org
- Subject: Re: c++/3099: cygwin: Many g++ EH failures
- From: rth at gcc dot gnu dot org
- Date: 13 Jun 2001 06:21:00 -0000
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