public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Andrew Haley <aph@redhat.com>
Cc: 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: Wed, 13 May 2009 17:59:00 -0000	[thread overview]
Message-ID: <4A0B0D34.4060800@gmail.com> (raw)
In-Reply-To: <4A0AF2BB.3080400@redhat.com>

Andrew Haley wrote:
> Dave Korn wrote:
>> Andrew Haley wrote:
>>
>>> Did you try my list of things to lift out?  I don't think there will be any
>>> interdependencies; the only problem might be that the reduction is not enough.
>>     Hi Andrew,
>>
>>   I've had a quick hack at it now, and it's not doing what I'd hoped, so
>> possibly I've misunderstood what you intended, or am not grokking the
>> structure of java packages correctly.
>>
>>
>>   So, did I do the partitioning wrong here?  Or have I misunderstood what you
>> were referring to as "interdependencies"?
> 
> Oh, I'm _so_ sorry, you're absolutely right.  I misread (or, perhaps, miswrote)
> the makemake.tcl file.  It turns out that even those files that are compiled BC
> are compiled with -fno-indirect-classes, so that they can be (and indeed are)
> called from code compiled with the C++ ABI.
> 
> How embarrassing.  :-(


  That's ok, thanks for trying to help.  I'll just have to go down the route
of preparing import libraries ahead-of-time.  (Actually I'm already doing this
as we speak, and it is /possibly/ showing up some binutils bugs, but that's
another story....)

  On the bright side, this means that if they're going to be interdependent
sublibraries anyway, I can parcel them out more evenly, and get a greater
reduction in the number of symbols each one individually exports.

    cheers,
      DaveK

  reply	other threads:[~2009-05-13 17:59 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 [this message]
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=4A0B0D34.4060800@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --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).