water cooler :: Would it be time for DSL to shed its skin?

What? omitting frame pointers increases size? Weird, it's supposed to leave them out so size would be smaller..

I think we can have little bigger code for speed, unless it's bigger than with glibc originals of course..

I wondered about your results, so I did a test, built gzip:
flags: binary size:
"-s -Os -fomit-frame-pointer" 45720
"-s -Os" 45880
"-s -Os -march=i486 -mtune=i686 -fomit-frame-pointer" 45720

so omitting frame pointers did decrease size, and optimizing didn't increase size......

Another comparison:

unoptimized wide ncurses library was 333kb with glibc and 284kb with uClibc..

C compiler: gcc 4.2.0 (self-compiled)
C++ compiler: g++ 3.3.5 (Debian Sarge)
Size taken with `du -b file` after running `sstrip file`.
`sstrip` ("Maximal 'strip'ing utility.") can be found here (www.busybox.net).
Note:
Bold entries are C++ apps.
'-mcpu' is used for C++ apps because g++-3.3 doesn't understand '-mtune'.
Comments:
It seems like '-fomit-frame-pointer' hits C++ apps. C apps seem unaffected.
Could this be due to a difference in compiler versions (gcc-4.2-4.2.0 vs g++-3.3-3.3.5)? I will have to compile g++-4.2 first and then find out.

unzip 5.52
`make` ; `sstrip unzip` ; `du -b unzip`
'-Os' 90596
'-Os -fomit-frame-pointer' 90596
'-Os -march=i486 -mtune=i686' 90596
'-Os -march=i486 -mtune=i686 -fomit-frame-pointer' 90596

p7zip 4.49
`make 7za` ; `sstrip bin/7za` ; `du -b bin/7za`
'-Os' 845289
'-Os -fomit-frame-pointer' 1062377
'-Os -march=i486 -mcpu=i686' 845289
'-Os -march=i486 -mcpu=i686 -fomit-frame-pointer' 1062377

unrar 3.7.6
`make` ; `sstrip unrar` ; `du -b unrar`
'-Os' 154459
'-Os -fomit-frame-pointer' 187227
'-Os -march=i486 -mcpu=i686' 154459
'-Os -march=i486 -mcpu=i686 -fomit-frame-pointer' 187227

That might be because of old g++, I don't seem to recall it raising sizes..

when can I have your root image to play with? X etc..

Next Page...
original here.