This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/13806] linking libgcj.so requires excessive time/memory
- From: "daney at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Jan 2004 17:55:02 -0000
- Subject: [Bug libgcj/13806] linking libgcj.so requires excessive time/memory
- References: <20040122022123.13806.jsturm@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From daney at gcc dot gnu dot org 2004-01-22 17:55 -------
I for one give a strong vote for breaking the library into separate parts. We
are using libgcj in an embedded application where there is no need for AWT. In
order to conserve space in ROM I have a custom build that strips all AWT classes
out of libgcj.
Having this done by the default build would make my life much easier.
A second problem that I am having that this would solve is the MIPS multi-got
problem. Because of command line limitations on the build platfrom (x86/linux)
a full libgcj build has to be done with incremental linking. Because of the way
MIPS PIC code is generated this forces us to use a large got (slower code)
instead of multi-got (faster code). Any thing that moves us away from
incremental linking of libgcj is a win for runtime speed (as well as building
faster)
Can we target 3.4.1 instead of 3.5.0?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13806