From: "ffileppo" <ffileppo@libero.it>
To: "aph" <aph@redhat.com>
Cc: "java" <java@gcc.gnu.org>
Subject: Re: gcj 4.4 and AWT toolkit
Date: Thu, 31 Jul 2008 18:21:00 -0000 [thread overview]
Message-ID: <K4VUYD$2BECBFFB52DEB8A6099DE511A06F70FF@libero.it> (raw)
> > As you said, it doesn't even seem to try to open libgtkpeer
> >
> > root@portatile-hp:/media/disk/x86-gcc-inst/bin# strace -f ./awt-test
>
> Debugging time; you're either going to have to do it yourself or
> persuade someone to help you.
>
> Andrew.
>
Any hints where to start understading this problem?
Just debugging with gdb?
I wonder if this bad behaviour is caused by the recent merge of classpath 0.97.2
I hope more people will concern about this issue; personally I can't wait to test the performance of AWT/SWING code compiled with gcj compared with bytecode execution (especially on embedded systems). We should team up to solve this problem :-)
If you're interested, please take a look at my other post (http://gcc.gnu.org/ml/java/2008-06/msg00031.html) about gcc 4.3.2 and 4.3.0/1 bug with AWT/SWING code (beacause of classpath 0.96?)
Thanks for your help,
Francesco
next reply other threads:[~2008-07-31 18:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 18:21 ffileppo [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-14 16:59 ffileppo
2008-08-14 17:03 ` Andrew Haley
2008-08-17 21:45 ` Mark Wielaard
2008-08-18 18:38 ` Andrew John Hughes
2008-08-21 17:13 ` Tom Tromey
2008-08-22 0:49 ` Andrew John Hughes
2008-08-22 1:15 ` Tom Tromey
2008-08-29 23:21 ` Andrew John Hughes
2008-08-14 13:24 ffileppo
2008-08-13 15:43 ffileppo
2008-08-14 13:13 ` Mark Wielaard
2008-08-01 11:33 ffileppo
2008-07-31 13:09 ffileppo
2008-07-31 14:30 ` Andrew Haley
2008-07-31 12:46 ffileppo
2008-07-31 12:51 ` Andrew Haley
2008-07-31 12:08 ffileppo
2008-07-31 12:17 ` Andrew Haley
2008-07-31 11:51 ffileppo
2008-07-31 11:55 ` Andrew Haley
2008-08-01 11:23 ` Mark Wielaard
2008-07-30 19:46 ffileppo
2008-07-31 8:40 ` 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='K4VUYD$2BECBFFB52DEB8A6099DE511A06F70FF@libero.it' \
--to=ffileppo@libero.it \
--cc=aph@redhat.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).