From: Andrew Haley <aph@redhat.com>
To: ffileppo <ffileppo@libero.it>
Cc: java <java@gcc.gnu.org>, classpath <classpath@gnu.org>
Subject: Re: [GCJ] Performance of GUI applications on embedded systems
Date: Wed, 05 Nov 2008 09:44:00 -0000 [thread overview]
Message-ID: <49116AC5.4090806@redhat.com> (raw)
In-Reply-To: <K9UQ08$AD832FCC143586E9A7A4E27782F3E256@libero.it>
ffileppo wrote:
>> Here's one improvement. If you can get rid of the places in the GTK peers
>> where class and method lookups are performed at runtime you'll probably
>> have a fix. This shouldn't be a massive amount of work, just rather
>> boring.
>>
>> In gcj,
>>
>> * Compiled java code is quite fast.
>> * Class lookup by name is slow.
>> * Calling JNI code from compiled java code is quite fast.
>> * Calling compiled java code from JNI code is slow.
>> * Exceptions are slow.
> I tried your improvement but now I'm getting Segmentation Fault whenever I execute any GUI application.
> (Non-gui code is working fine)
>
> Do you have any idea to investigate this problem?
It didn't do that to me.
Where does the segfault occur?
Do you still get the segfault after backing out the patch?
Andrew.
next prev parent reply other threads:[~2008-11-05 9:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 8:24 ffileppo
2008-11-05 9:44 ` Andrew Haley [this message]
2008-11-05 9:45 ` Mark Wielaard
2008-11-05 9:50 ` Andrew Haley
-- strict thread matches above, loose matches on Subject: below --
2008-11-10 8:55 ffileppo
2008-11-10 10:20 ` Andrew Haley
2008-11-07 11:04 ffileppo
2008-11-07 11:18 ` Andrew Haley
2008-11-07 18:56 ` Andrew Haley
2008-11-08 11:40 ` Andrew Haley
2008-11-08 12:47 ` Andrew Haley
2008-11-09 0:25 ` Andrew John Hughes
2008-11-09 10:11 ` Mark Wielaard
2008-11-09 13:55 ` Andrew Haley
2008-11-06 13:40 ffileppo
2008-11-06 16:40 ` Andrew Haley
2008-11-06 17:02 ` Christian Thalinger
2008-11-05 13:53 ffileppo
2008-11-05 14:07 ` Andrew Haley
2008-11-05 14:26 ` Andrew Haley
2008-11-03 12:51 ffileppo
2008-11-03 14:53 ` Andrew Haley
2008-11-03 15:04 ` Andrew Haley
2008-11-03 7:38 ffileppo
2008-11-03 10:37 ` Andrew Haley
2008-11-03 12:02 ` Andrew Haley
2008-11-03 12:54 ` Andrew Haley
2008-11-03 13:02 ` Roman Kennke
2008-11-03 13:14 ` Andrew Haley
2008-11-03 15:46 ` 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=49116AC5.4090806@redhat.com \
--to=aph@redhat.com \
--cc=classpath@gnu.org \
--cc=ffileppo@libero.it \
--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).