public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Bryce McKinlay <bmckinlay@gmail.com>
Cc: Andrew Haley <aph@redhat.com>, java@gcc.gnu.org
Subject: Re: _Unwind_FindEnclosingFunction vs darwin
Date: Sun, 20 Dec 2009 00:30:00 -0000	[thread overview]
Message-ID: <20091220003031.GA494@bromo.med.uc.edu> (raw)
In-Reply-To: <7230133d0912191154s18d9c245m9149b5b7f6b0680f@mail.gmail.com>

On Sat, Dec 19, 2009 at 07:54:15PM +0000, Bryce McKinlay wrote:
> 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

   I confused about the details of functions called within a static inline function.
Do we have to create additional static inlines for each of those called functions
in the same header? If so, we are going to have to add a lot of code from
unwind-dw2-fde-darwin.c since _Unwind_Find_FDE() calls _Unwind_Find_registered_FDE().
Perhaps it would be easier if we added a duplicated _Unwind_FindEnclosingFunction()
to unwind-dw2-fde-darwin.c as _darwin10_Unwind_FindEnclosingFunction() and emitted
that symbol via the versioned libgcc_ext stubs. I know that works in theory and would
be a much smaller patch.
               Jack

  reply	other threads:[~2009-12-20  0:30 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 [this message]
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=20091220003031.GA494@bromo.med.uc.edu \
    --to=howarth@bromo.med.uc.edu \
    --cc=aph@redhat.com \
    --cc=bmckinlay@gmail.com \
    --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).