Thank you. I'll stick to -march=native for now
Walter Dnes <waltd...@waltdnes.org> wrote:
>On Fri, Dec 19, 2014 at 02:38:48AM +0400, German wrote
>> Couldn't find those in documentation. Thank you
>
> If you're building on the target machine, use the "native" CFLAG. It
>has been around for a while. It detects the CPU, and builds for it
>"automagically". You don't have to do any more grunt work, figuring out
>the flags for your CPU. Computers are supposed to do the hard work. I
>use...
>
>FLAGS="-O2 -march=native -mfpmath=sse -fomit-frame-pointer -pipe
>-fno-unwind-tables -fno-asynchronous-unwind-tables"
>CXXFLAGS="${CFLAGS}"
>
> Mind you, if you're cross-compiling on another system, and then moving
>the binaries over, you will have to figure out the correct flags. See
>below for a method.
>
> Another problem is that there are also cpu-specific USE flags. You
>can get a good start on figuring them out, as well as CFLAGS, by running
>
>grep flags /proc/cpuinfo
>
>on the target machine. There will be one line of output for each core.
>You'll have multiple identical lines of output.
>
>--
>Walter Dnes <waltd...@waltdnes.org>
>I don't run "desktop environments"; I run useful applications
>
