Another reason to not use gcc-2.5.8

Paul Gortmaker (gpg109@rsphy6.anu.edu.au)
Mon, 29 Apr 1996 23:33:57 +1000 (EST)

Alan added eariler that you shouldn't use gcc-2.5.8 on recent v1.3.x
kernels due to possibilities of bad code. Here is some more incentive.
It appears that you can save some memory by using a newer gcc as well.

-Memory: 6780k/8192k available (724k kernel code, 384k reserved, 304k data)
+Memory: 6836k/8192k available (668k kernel code, 384k reserved, 304k data)

-Linux version 1.3.96 (root@ratbag) (gcc version 2.5.8) #1 Sun [...]
+Linux version 1.3.96 (root@ratbag) (gcc version 2.7.2) #2 Mon [...]

The above are for an identical ".config" file, and as can be seen, there
appears to be a saving of about 56kB just from switching compilers.

Here are all the enabled options for the above case, in case anyone is
interested. The gcc-2.7.2 is a homebuilt a.out binary version. I haven't
compared the System.map files to see where the 56kB comes from.

Paul.

==================================================================

CONFIG_NET CONFIG_BINFMT_AOUT CONFIG_M486 CONFIG_BLK_DEV_FD
CONFIG_BLK_DEV_IDE CONFIG_INET CONFIG_SCSI CONFIG_BLK_DEV_SD
CONFIG_SCSI_CONSTANTS CONFIG_SCSI_BUSLOGIC CONFIG_NETDEVICES
CONFIG_NET_ISA CONFIG_NE2000 CONFIG_EXT2_FS CONFIG_FAT_FS CONFIG_MSDOS_FS
CONFIG_PROC_FS CONFIG_NFS_FS CONFIG_SERIAL CONFIG_RTC