On Mon, Sep 29, 2014 at 04:32:40PM +0100, Jorge Almeida wrote > On Mon, Sep 29, 2014 at 4:15 PM, Walter Dnes <waltd...@waltdnes.org> wrote: > > On Mon, Sep 29, 2014 at 12:45:44PM +0100, Jorge Almeida wrote > > > > > > Grasping at straws now. What are your CFLAGS and full USE flags? I > > suggest running the command... > > > > emerge --info | grep "^\(CFLAGS\|USE\)" > > > > This captures default USE flags that aren't explicitly listed in your > > make.conf. Out of sheer curiusity, what sizes do you get if you use > > "-O2"? I believe that turns off loop-unrolling. > > > No difference with -O2. The program I'm using (as test) is really > simple (a terminal wall clock), although the same problem happens with > other programs. > > Are the USE flags relevant for a program that is orthogonal to emerge?
Probably not. > Anyway, here it goes: > > # emerge --info | grep "^\(CFLAGS\|USE\)" > CFLAGS="-O2 -march=native -pipe -fomit-frame-pointer" > USE="berkdb bindist bzip2 cli cracklib crypt cxx dri fortran gdbm gpm > iconv modules ncurses nptl openmp pcre readline session ssl unicode > x86 zlib" ABI_X86="32" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem I was thinking of stuff like "mmx mmxext sse sse2 sse3 ssse3" etc. This might accomplish the same work with fewer bytes of advanced machine language instructions, versus more bytes of standard instructions. -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
