From: Jack Howarth <howarth@bromo.med.uc.edu>
To: rguenth@gcc.gnu.org, gcc@gcc.gnu.org
Subject: the cause of PR41260 is new additional epilog unwind information
Date: Fri, 18 Sep 2009 22:55:00 -0000 [thread overview]
Message-ID: <20090918225532.GA12673@bromo.med.uc.edu> (raw)
Richard,
We have an analysis on the cause of the breakage of
exception handling at r147995 on x86_64-apple-darwin10 (PR41260)...
http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025908.html
http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025909.html
The additional epilog unwind information is breaking the
'running' of the dwarf unwind info. The options to fix it are either
to 1) not add epilog unwind information for Darwin or 2) have the
gcc driver implicitly add -no_compact_unwind to the link line for
Darwin.
Can you propose a patch to achieve the first solution of not
adding the additional epilog unwind information on darwin so I
can test that solution? Thanks in advance.
Jack
next reply other threads:[~2009-09-18 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 22:55 Jack Howarth [this message]
2009-09-19 17:38 ` Richard Guenther
2009-09-18 23:14 Jack Howarth
2009-09-19 2:30 Jack Howarth
2009-09-19 12:27 ` Joseph S. Myers
2009-09-19 13:50 ` Peter O'Gorman
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=20090918225532.GA12673@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=gcc@gcc.gnu.org \
--cc=rguenth@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).