bug#311: [Lnx-bbc-devel] -mcpu and ISO sizes
Seth David Schoen <[email protected]>
| Newsgroups | gmane.linux.bbc.bugs |
|---|---|
| Message-ID | <[email protected]> |
So continuing to investigate: If I run gcc -v inside and outside of the chroot, the only substantive difference is that the version of the GNU assembler which is invoked differs by one point in its minor version (and reports that it's using a correspondingly difference version of the BFD library). The GNU assembler version outside my chroot is 2.13.90.0.10 and inside is 2.12.90.0.1. The version 2.13.90.0.10 appears to be producing smaller binaries. I also ran gcc -v -save-temps and looked at all the intermediate files. Remember that my non-chroot build system produces smaller binaries overall. The .c files were identical (of course). The .i file in the chroot was 105 bytes smaller. The .s files were byte-for-byte identical. The .o file in the chroot was 60 bytes larger. The final binary in the chroot was 32 bytes larger. Running the same build on gar (outside the chroot) produces all intermediate files with exactly the same sizes as the non-chroot build on requiem. Running it on garson (outside the chroot) produces the same thing. -- Seth David Schoen <[email protected]> | Reading is a right, not a feature! http://www.loyalty.org/~schoen/ | -- Kathryn Myronuk http://vitanuova.loyalty.org/ |