From: Bryce McKinlay <bmckinlay@gmail.com>
To: Jack Howarth <howarth@bromo.med.uc.edu>
Cc: Andrew Haley <aph@redhat.com>, java@gcc.gnu.org
Subject: Re: _Unwind_FindEnclosingFunction vs darwin
Date: Sat, 19 Dec 2009 19:54:00 -0000 [thread overview]
Message-ID: <7230133d0912191154s18d9c245m9149b5b7f6b0680f@mail.gmail.com> (raw)
In-Reply-To: <20091219184907.GA31305@bromo.med.uc.edu>
On Sat, Dec 19, 2009 at 6:49 PM, Jack Howarth <howarth@bromo.med.uc.edu> wrote:
> to libjava/include/posix.h, what is the correct way to access the missing declarations
> for dwarf_eh_bases, dwarf_fde, fde and _Unwind_Find_FDE? Are we supposed to directly
> include the *dw2* headers from the gcc subdirectory or duplicate their contents in this
> header?
I think you only really need to copy the dwarf_eh_bases struct and the
definition for _Unwind_Find_FDE itself. The others can be treated as
opaque.
Please also call it _Jv_Unwind_Find_FDE and use configure.ac to enable
it for Darwin (only) as I described before - its bad to override
functions with #defines...
Bryce
next prev parent reply other threads:[~2009-12-19 19:54 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 [this message]
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
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=7230133d0912191154s18d9c245m9149b5b7f6b0680f@mail.gmail.com \
--to=bmckinlay@gmail.com \
--cc=aph@redhat.com \
--cc=howarth@bromo.med.uc.edu \
--cc=java@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).