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