public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/19368] GCJ doesn't build working "hello world" on OS X
Date: Tue, 11 Jan 2005 19:00:00 -0000 [thread overview]
Message-ID: <20050111190018.18775.qmail@sourceware.org> (raw)
In-Reply-To: <20050111045400.19368.bothner@gcc.gnu.org>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-11 19:00 -------
(In reply to comment #4)
> Indeed, it just takes forever: About 40+ seconds on my 1Gz G4 PowerBook.
> Linking with -Wl,-bind_at_load doesn't make much difference.
You have to link libgcj with -single_module to get the speed up. This is a dyld (dynamic loader aka
ld.so) problem and not really a java problem.
> I thought it worked before (I don't consider 40 seconds start-up time "working")
> but perhaps I'm mistaken.
The start up time comes from looking up symbols in the dynamic library and it is really a bug in dyld
and the only work around I know of is to link libgcj with -single_module, I can post a patch for that but
that will take a while because there are more important things with respect with the release of GCC than
the slow start-up time of gcj on Pather (Tiger it is fixed).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19368
next prev parent reply other threads:[~2005-01-11 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 4:54 [Bug java/19368] New: " bothner at gcc dot gnu dot org
2005-01-11 13:02 ` [Bug java/19368] " pinskia at gcc dot gnu dot org
2005-01-11 13:03 ` pinskia at gcc dot gnu dot org
2005-01-11 14:11 ` andreast at gcc dot gnu dot org
2005-01-11 18:02 ` bothner at gcc dot gnu dot org
2005-01-11 19:00 ` pinskia at gcc dot gnu dot org [this message]
2005-01-11 19:15 ` andreast at gcc dot gnu dot org
2005-01-11 19:17 ` andreast at gcc dot gnu dot org
2005-01-19 1:43 ` pinskia at gcc dot gnu dot org
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=20050111190018.18775.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).