From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Andrew Haley <aph@redhat.com>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
java@gcc.gnu.org, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [JAVA,libtool] Big libjava is biiiig.
Date: Wed, 06 May 2009 16:45:00 -0000 [thread overview]
Message-ID: <4A01C128.2020500@gmail.com> (raw)
In-Reply-To: <4A01BD26.30707@redhat.com>
Andrew Haley wrote:
> Dave Korn wrote:
>
>> 1) Would this be a reasonable approach, specifically i) in adding a configure
>> option to cause sublibraries to be built, and ii) in using gmake's $(filter)
>> construct to crudely subdivide the libraries like this?
>
> At program startup the first library would be loaded, it would load
> the next, and so on. There are a few parts of libgcj that are truly
> independent, but I suspect that you'd always load almost all of it.
> So, you'd have longer startup time for loading all those files.
Compared to a single DLL that is unusably malformed because it exceeds
system limits, that's still an improvement :)
> With regard to GNU libc platforms:
>
> You'd no longer be able to make so much use of fast calls between
> functions in the same library; you'd have to go via the PLT.
>
> Also, dl_iterate_phdr() is used a great deal (for finding exception
> regions, garbage collection, etc.) and it linearly scans the libraries
> that are loaded. So, the more libraries you have loaded, the slower
> it goes.
>
> Now, I don't know how much of these characteristics are shared by
> Windows, but I imagine some of them are.
Yes, the inter-library calls would have to be dllimports and go through
stubs (one extra indirect branch). I don't know how dl_iterate_phdr works on
win32 but I imagine that it's also linear in the number of libs.
> So, I suspect your best bet would be to split libgcj into core and
> non-core libraries and not slice much more thinly than that. I can
> advise you what is core and what isn't.
Please do, I'll happily try that approach since it might significantly
simplify my inter-dependences problems.
cheers,
DaveK
next prev parent reply other threads:[~2009-05-06 16:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A01B55C.6060700@gmail.com>
2009-05-06 15:58 ` Dave Korn
2009-05-06 16:15 ` Ralf Wildenhues
2009-05-06 16:27 ` David Daney
2009-05-06 16:31 ` Richard Guenther
2009-05-06 16:40 ` Andrew Haley
2009-08-22 13:24 ` Dave Korn
2009-08-22 16:33 ` Andrew Haley
2009-08-22 18:55 ` Dave Korn
2009-08-28 18:04 ` Tom Tromey
2009-08-28 18:16 ` David Daney
2009-08-28 19:56 ` Dave Korn
2009-05-06 16:57 ` Dave Korn
2009-05-07 21:49 ` Ralf Wildenhues
2009-05-11 17:14 ` Dave Korn
2009-05-11 17:26 ` Andrew Haley
2009-05-11 18:03 ` Dave Korn
2009-05-13 12:38 ` Dave Korn
2009-05-13 16:18 ` Andrew Haley
2009-05-13 17:59 ` Dave Korn
2009-05-13 15:39 ` Dave Korn
2009-05-06 16:39 ` Andrew Haley
2009-05-06 16:45 ` Dave Korn [this message]
2009-05-06 17:12 ` Andrew Haley
2009-05-11 17:33 ` Dave Korn
2009-05-11 17:39 ` Andrew Haley
[not found] ` <7230133d0905060959h5371a608nff03cce1e1e98f47@mail.gmail.com>
2009-05-06 17:08 ` Dave Korn
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=4A01C128.2020500@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--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).