From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Tom Tromey <tromey@redhat.com>,
Dave Korn <dave.korn.cygwin@googlemail.com>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
java@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: [JAVA,libtool] Big libjava is biiiig.
Date: Fri, 28 Aug 2009 19:56:00 -0000 [thread overview]
Message-ID: <4A9839A5.9000005@gmail.com> (raw)
In-Reply-To: <4A981E93.7080205@caviumnetworks.com>
David Daney wrote:
> Tom Tromey wrote:
>>>>>>> "Dave" == Dave Korn <dave.korn.cygwin@googlemail.com> writes:
>>
>> Dave> There are a couple of regressions to solve first, but it appears
>> Dave> that I've more-or-less cracked it. Full details are written up
>> Dave> here:
>>
>> Dave> http://gcc.gnu.org/wiki/Internal_dependencies_of_libgcj
>>
>> One thing worth considering is that you may be able to shrink things
>> even more by splitting up some existing objects.
>>
>> I didn't see AWT in the cluster 48 list, which seems weird.
>> I would expect it to be in the core due to AWTPermission.
>>
>> I'm curious why sun.awt and swing ended up in there.
All the raw data is there to take a look at if you're determinedly curious.
I don't know a lot about the theory behind the graphviz sccmap tool, and how
exactly it breaks the graph up.
>> I would expect that with minor tweaks you could probably get AWT, the
>> peers, and Swing to drop out. That was true for AWT, at least, last
>> time I looked at this (years ago) -- but I needed a special case to keep
>> AWTPermission in.
>
> I have patches that do a lot of the things Tom mentions. They are only
> lightly tested, but they could be a starting point.
>
> I will dig them out and post them this weekend.
Thanks for the suggestions! I'm going to finish the last tweaks and submit
my patch with the list as it currently stands, because of the scale of the
change and the looming-yet-still-a-little-vague end of stage1, but I think
tweaking the list of files subsequently is something we can do incrementally
once it's reviewed and checked in, no?
cheers,
DaveK
next prev parent reply other threads:[~2009-08-28 19:56 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 [this message]
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
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=4A9839A5.9000005@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=ddaney@caviumnetworks.com \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=tromey@redhat.com \
/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).