This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: I can make your gcj-compiled binaries much smaller.


Adam Megacz writes:
 > 
 > Andrew Haley <aph@redhat.com> writes:
 > >  > You have this problem whenever you link statically, whether you use my
 > >  > technique or not.
 > 
 > > Indeed yes, which is why static linkage doesn't work either.
 > 
 > Fine, "my proposal will work as well as static linkage currently
 > works, with the advantage of smaller binaries" </pedantic>

Okay, kind sorta.

 > Honestly, let's not start arguing about what "works" means.

 > > However, I don't think we should get into the situation where libgcj
 > > contains static class references
 > 
 > You don't have to.  The application developer will do this.

I don't believe that's true, and I explained why.  When libgcj uses
reflection as a means of resolving references _internally_, there will
have to be a static class reference.

Andrew.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]