I saw this a couple of days ago on the busybox mailing list. See... http://comments.gmane.org/gmane.linux.busybox/36695
> By default, modern GCC generates DWARF2 debug/unwind tables in the > .eh_frame section of the object files/binaries. This adds significant > bloat (as much as 15%) to the size of the busybox binary, including > the portion mapped/loaded into memory at runtime (possibly a big > issue for NOMMU targets), and the section is not strippable with > the strip command due to being part of the loaded program text. [...deletia...] > it seems the solution is to add to the CFLAGS -fno-unwind-tables > and -fno-asynchronous-unwind-tables. I realize that busybox is used in embedded environments, and physical size and memory footprint is critical there. How do Gentoo devs feel about it? Would there be any problems with users adding -fno-unwind-tables and -fno-asynchronous-unwind-tables to CFLAGS and CXXFLAGS? Should it be mentioned in the install manual as an option for users to possibly include? -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
