public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joey dot ye at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38952] [4.4 Regression] EH does not work.
Date: Mon, 26 Jan 2009 11:49:00 -0000	[thread overview]
Message-ID: <20090126114921.8870.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38952-9431@http.gcc.gnu.org/bugzilla/>



------- Comment #20 from Joey dot ye at intel dot com  2009-01-26 11:49 -------
(In reply to comment #10)
> This is caused by stack alignment change, revision 138335. Joey and
> Xuepeng will look into it after holiday, Feb. 1.
This must be stack alignment change. Looks we didn't handle stack unwinding on
Cygwin correctly.

Dave, comparing the the EH mechanism in Linux, what's the difference of SjLj EH
in Cygwin? Answer to this question might help solving the problem sooner.

Thanks - Joey


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38952


  parent reply	other threads:[~2009-01-26 11:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 23:20 [Bug target/38952] New: " dave dot korn dot cygwin at gmail dot com
2009-01-23 23:31 ` [Bug target/38952] " dave dot korn dot cygwin at gmail dot com
2009-01-23 23:31 ` dave dot korn dot cygwin at gmail dot com
2009-01-23 23:32 ` dave dot korn dot cygwin at gmail dot com
2009-01-23 23:44 ` dave dot korn dot cygwin at gmail dot com
2009-01-24  0:10 ` dave dot korn dot cygwin at gmail dot com
2009-01-24  1:08 ` dave dot korn dot cygwin at gmail dot com
2009-01-24  6:24 ` dave dot korn dot cygwin at gmail dot com
2009-01-24  8:47 ` rguenth at gcc dot gnu dot org
2009-01-24 17:07 ` ubizjak at gmail dot com
2009-01-24 18:12 ` dave dot korn dot cygwin at gmail dot com
2009-01-24 21:41 ` hjl dot tools at gmail dot com
2009-01-25  5:33 ` dave dot korn dot cygwin at gmail dot com
2009-01-25  5:56 ` dave dot korn dot cygwin at gmail dot com
2009-01-25  5:58 ` dave dot korn dot cygwin at gmail dot com
2009-01-25  6:05 ` dave dot korn dot cygwin at gmail dot com
2009-01-25  6:34 ` dave dot korn dot cygwin at gmail dot com
2009-01-25  6:40 ` dave dot korn dot cygwin at gmail dot com
2009-01-25  7:47 ` dave dot korn dot cygwin at gmail dot com
2009-01-25 21:36 ` dave dot korn dot cygwin at gmail dot com
2009-01-25 23:08 ` dave dot korn dot cygwin at gmail dot com
2009-01-26 11:49 ` Joey dot ye at intel dot com [this message]
2009-01-26 19:03 ` dave dot korn dot cygwin at gmail dot com
2009-01-26 22:29 ` hjl dot tools at gmail dot com
2009-01-26 23:39 ` hjl at gcc dot gnu dot org
2009-01-31 17:21 ` ktietz at gcc dot gnu dot org
2009-01-31 17:34 ` hjl at gcc dot gnu dot org
2009-01-31 17:35 ` hjl dot tools at gmail dot com

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=20090126114921.8870.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).