Re: egcs 1.0.2 c++ .o size

[Brian Glendenning <bglenden@aoc.nrao.edu>]

> Use -fsjlj-exceptions, and compare against your application without

This didn't help (I didn't turn off our emulation, but it is very
cheap).

Here are the figures for an individual .o (all -O2)

gcc 2.7.2                         29k
egcs 1.0.2                        47k
egcs -fno-exceptions -fno-rtti    26k
egcs -fsjlj-exceptions            41k

These size ratio basically follow all the way through to the final
executables. The result of objdump -h is:

Table.egcs.o:     file format elf32-sparc

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .text         0000316c  00000000  00000000  000000f4  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE
  1 .rodata       0000026f  00000000  00000000  00003260  2**3
                  CONTENTS, ALLOC, LOAD, RELOC, READONLY, DATA
  2 .data         00000004  00000000  00000000  000034d0  2**2
                  CONTENTS, ALLOC, LOAD, DATA
  3 .dtors        00000004  00000000  00000000  000034d4  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, DATA
  4 .ctors        00000004  00000000  00000000  000034d8  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, DATA
  5 .gcc_except_table 000005a0  00000000  00000000  000034dc  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, DATA
  6 .eh_frame     00000a5c  00000000  00000000  00003a7c  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, DATA
  7 .bss          00000001  00000000  00000000  000044d8  2**0
                  ALLOC
  8 .comment      00000050  00000000  00000000  0000b500  2**0
                  CONTENTS, READONLY

Is this typical, or are we somehow doing something that tickles
particularly bad space behaviour of the exception handling code?

Brian