From: Tom Tromey <tromey@redhat.com>
To: Andrew Haley <aph@redhat.com>
Cc: Herman ten Brugge <hermantenbrugge@home.nl>, java@gcc.gnu.org
Subject: Re: very slow jni code callbacks
Date: Mon, 28 Sep 2009 19:01:00 -0000 [thread overview]
Message-ID: <m3iqf2lwps.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4AC0A614.2040108@redhat.com> (Andrew Haley's message of "Mon, 28 Sep 2009 13:03:32 +0100")
Andrew> This calls _Jv_GetTypesFromSignature, which in turn iterates though
Andrew> all the class loaders looking up the types of all the arguments.
Andrew> But as far as I can see this is a pointless waste of time: the only
Andrew> use of the type of each argument is to determine whether it's a
Andrew> primitive type or not, and we could certainly have done that when
Andrew> we created the jmethodID.
Yeah, this could use some improvement.
Even a variant of _Jv_GetTypesFromSignature that did less work would
help.
Tom
next prev parent reply other threads:[~2009-09-28 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 13:23 Herman ten Brugge
2009-09-28 12:03 ` Andrew Haley
2009-09-28 12:10 ` Bryce McKinlay
2009-09-28 12:13 ` Andrew Haley
2009-09-28 19:01 ` Tom Tromey
2009-09-28 19:01 ` Tom Tromey [this message]
2009-09-28 19:47 ` Herman ten Brugge
2009-09-28 20:13 ` Andrew Haley
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=m3iqf2lwps.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=aph@redhat.com \
--cc=hermantenbrugge@home.nl \
--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).