binary sizes

Thu Feb 19 04:47:00 GMT 2004

Anthony Green <green@redhat.com> writes:
> It should be merging UTF8 literals for ELF targets. Are there other
> read-only bits that come to mind?

Isn't all the reflection data read-only? I guess there's nothing to
merge there, so it probably doesn't matter... I was just curious why
it's in .data.
BTW, I have the freedom to "break" Java semantics quite a bit for my
app... for example, we don't need anything post-jdk1.1, and we don't
use reflection. So if anybody has ideas on ways I can damage gcj in
order to shrink the binary, that would be really great.
If UTF8 stuff really is in .rodata (I'm using gcj 3.3.2 on linux/x86),
then UTF8 constants aren't contributing much to my binary size (and
they'll compress well anyways)... what else could be in that massive
read-write data segment?
I guess I could also try pruning unreachable static fields, although
somehow I don't think that will make a huge difference.
 - a