From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Andrew Haley <aph@redhat.com>
Cc: Bryce McKinlay <bmckinlay@gmail.com>,
java@gcc.gnu.org, mrs@apple.com,
developer@sandoe-acoustics.co.uk
Subject: Re: _Unwind_FindEnclosingFunction vs darwin
Date: Sun, 20 Dec 2009 16:12:00 -0000 [thread overview]
Message-ID: <20091220161234.GA27121@bromo.med.uc.edu> (raw)
In-Reply-To: <4B2E25AC.6030500@redhat.com>
On Sun, Dec 20, 2009 at 01:25:00PM +0000, Andrew Haley wrote:
>
> This is all far too heavyweight; rather than simply solving the problem, it's
> speculating about some other problems that may not exist.
>
> Andrew.
Andrew,
One other comment. It seems equally heavy-handed to drag in significant
sections of the code from unwind-dw2.c and its associated headers. Also the
solution will never be generic since _Unwind_FindEnclosingFunction() is
declared in unwind-compat.c, unwind-dw2.c and unwind-sjlj.c. I would have
a lot more faith in following this approach if it were first demonstrated
to be workable on linux.
Jack
next prev parent reply other threads:[~2009-12-20 16:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 14:46 Jack Howarth
2009-12-18 15:01 ` Andrew Haley
2009-12-18 15:54 ` Jack Howarth
2009-12-18 20:41 ` Jack Howarth
2009-12-19 10:51 ` Andrew Haley
2009-12-19 10:58 ` Bryce McKinlay
2009-12-19 11:07 ` Andrew Haley
2009-12-19 13:47 ` Jack Howarth
2009-12-19 17:26 ` Andrew Haley
2009-12-19 18:49 ` Jack Howarth
2009-12-19 19:54 ` Bryce McKinlay
2009-12-20 0:30 ` Jack Howarth
2009-12-20 2:03 ` Jack Howarth
2009-12-20 12:14 ` Bryce McKinlay
2009-12-20 13:20 ` Andrew Haley
2009-12-20 13:25 ` Andrew Haley
2009-12-20 16:03 ` Jack Howarth
2009-12-20 16:12 ` Jack Howarth [this message]
2009-12-20 17:47 ` Andrew Haley
2009-12-19 19:57 ` Jack Howarth
2009-12-20 13:26 ` Andrew Haley
2009-12-19 0:22 ` Jack Howarth
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=20091220161234.GA27121@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=aph@redhat.com \
--cc=bmckinlay@gmail.com \
--cc=developer@sandoe-acoustics.co.uk \
--cc=java@gcc.gnu.org \
--cc=mrs@apple.com \
/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).