public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <20010613062100.16216.qmail@sourceware.cygnus.com> (raw)

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


             reply	other threads:[~2001-06-12 23:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 23:21 rth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-01 10:26 Gerald Pfeifer
2001-06-12  3:51 mmitchel
2001-06-11 13:02 rth
2001-06-09 12:26 David.Billinghurst

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010613062100.16216.qmail@sourceware.cygnus.com \
    --to=rth@gcc.gnu.org \
    --cc=David.Billinghurst@riotinto.com \
    --cc=cgf@redhat.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).