public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "green at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/24616] linking BC-compiled classes: NoClassDefFoundErrors should be deferred
Date: Mon, 07 Nov 2005 15:06:00 -0000	[thread overview]
Message-ID: <20051107150630.704.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24616-10268@http.gcc.gnu.org/bugzilla/>



------- Comment #12 from green at redhat dot com  2005-11-07 15:06 -------
(In reply to comment #11)
> You're not describing this clearly.  :-)
> 
> We need to point the execution vector at a piece of code that throws an
> exception with the appropriate args.  Now, how should we do that?

The closure mechanism was specifically designed for when you want to call
interpreted code.  We don't want to do this here; we just want to throw an
exception with the right argument (stored in the closure object).

The current patch uses the closure mechanism to call the trampoline, which in
turn uses the ffi_call mechanism to call the exception throwing function.  But
we don't need to use ffi_call here, we can just call the exception throwing
function directly.  Then you'll realize that these functions don't need to be
separate at all.  Then you'll realize that you don't need to bother setting up
the ffi_cif - all you need is the exception argument.  

Does this help explain?


-- 


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


  parent reply	other threads:[~2005-11-07 15:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 16:20 [Bug libgcj/24616] New: " thebohemian at gmx dot net
2005-11-01 16:22 ` [Bug libgcj/24616] " tromey at gcc dot gnu dot org
2005-11-01 19:32 ` thebohemian at gmx dot net
2005-11-01 19:38 ` thebohemian at gmx dot net
2005-11-02 11:09 ` thebohemian at gmx dot net
2005-11-05 14:57 ` thebohemian at gmx dot net
2005-11-05 16:00 ` thebohemian at gmx dot net
2005-11-06 16:15 ` aph at gcc dot gnu dot org
2005-11-07 10:34 ` thebohemian at gmx dot net
2005-11-07 10:40 ` aph at gcc dot gnu dot org
2005-11-07 12:51 ` thebohemian at gmx dot net
2005-11-07 14:47 ` green at redhat dot com
2005-11-07 14:52 ` aph at gcc dot gnu dot org
2005-11-07 15:06 ` green at redhat dot com [this message]
2005-11-07 20:03 ` thebohemian at gmx dot net
2005-11-08 10:15 ` thebohemian at gmx dot net
2005-11-08 12:54 ` green at redhat dot com
2005-11-09 15:18 ` thebohemian at gmx dot net
2005-11-09 15:22 ` thebohemian at gmx dot net
2005-11-09 15:28 ` aph at gcc dot gnu dot org
2005-11-16 16:35 ` thebohemian at gmx dot net
2005-11-16 16:51 ` thebohemian at gmx dot net
2005-11-16 17:20 ` aph at gcc dot gnu dot org
2005-11-17 12:39 ` thebohemian at gmx dot net
2005-11-17 13:46 ` aph at gcc dot gnu dot org
2005-12-02 17:43 ` aph at gcc dot gnu dot org
2005-12-05 11:34 ` thebohemian at gmx dot net
2005-12-05 11:52 ` thebohemian at gmx dot net
2005-12-05 13:52 ` [Bug libgcj/24616] linking non-existing " thebohemian at gmx dot net
2006-01-31 16:46 ` thebohemian at gmx dot net
2006-02-01 13:45 ` thebohemian at gmx dot net

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=20051107150630.704.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).