public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Adam Megacz <gcj@lists.megacz.com>
Cc: java@gcc.gnu.org
Subject: Re: MissingResourceException with Date under mingw port
Date: Wed, 10 Apr 2002 10:49:00 -0000	[thread overview]
Message-ID: <87ofgr78i9.fsf@creche.redhat.com> (raw)
In-Reply-To: Adam Megacz's message of "10 Apr 2002 10:26:59 -0700"

>>>>> "Adam" == Adam Megacz <gcj@lists.megacz.com> writes:

Adam> Here's the standard prelude I throw into all my gcj programs to
Adam> force the linker to include all the required classes:
Adam> [ ... ]

Adam> To the other GCJ people: are there any disadvantages to putting
Adam> private static foo.class references in the java.* classes so that
Adam> static links work properly without this hack?

We already do this; look at FirstThread.java.  So far we've only done
it for classes needed for bootstrapping.  There's a tension here
because people might want to use static linking to make their programs
smaller; the more classes we list like this the less possible that is.

On the to-do list for a long time has been adding a command-line
option to gcj so you could specify classes which we would force to be
linked in.

I don't have an opinion right now on whether we should add your
classes to FirstThread.  I'd love to hear arguments either way.

Long term I think we need to make libgcj into a DLL on Windows.

Tom

  reply	other threads:[~2002-04-10 17:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 10:31 Adam King
2002-04-10 10:42 ` Adam Megacz
2002-04-10 10:49   ` Tom Tromey [this message]
2002-04-10 12:25   ` Eric Blake
2002-04-10 12:55     ` Adam Megacz
2002-04-10 15:56       ` Eric Blake
2002-04-10 16:11         ` Tom Tromey
2002-04-10 16:35     ` Tom Tromey
2002-04-10 18:21       ` Per Bothner
2002-04-10 11:11 ` Mark Wielaard

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=87ofgr78i9.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gcj@lists.megacz.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).