-m64 [enabled]
-m80387 [enabled]
-m96bit-long-double [enabled]
-maes [enabled]
-malign-stringops [enabled]
-mavx [enabled]
-mcx16 [enabled]
-mf16c [enabled]
-mfancy-math-387 [enabled]
-mfentry [enabled]
-mfp-ret-in-387 [enabled]
-mfsgsbase [enabled]
-mglibc [enabled]
-mhard-float [enabled]
-mieee-fp [enabled]
-mpclmul [enabled]
-mpopcnt [enabled]
-mpush-args [enabled]
-mrdrnd [enabled]
-mred-zone [enabled]
-msahf [enabled]
-msse [enabled]
-msse2 [enabled]
-msse3 [enabled]
-msse4 [enabled]
-msse4.1 [enabled]
-msse4.2 [enabled]
-mssse3 [enabled]
-mstackrealign [enabled]
-mtls-direct-seg-refs [enabled]
All of the features that ivy bridge are supported are there MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AES, PCLMUL, FSGSBASE, RDRND and F16C.
I am unsure however if there are any other optimisations which occur differently between corei7-avx and core-avx-i as i am not going to try and understand the full inner workings of gcc.
However i did manage to patch gcc to enable core-avx-i support when asking for -march=native except that i am unsure of and repercussions of doing so https://github.com/crondog/misc-patches
]]>makes no difference, the cflags are the same for each generation.
Not true...per the docs for gcc:
corei7-avx = sandy
core-avx-i = ivy
Different optimizations for sure, dunno about real-world impact though. The OP's question goes beyond the repo packages for linux-ck. Anything he/she builds via ABS or AUR (assuming a setting of -march=native in /etc/makepkg.conf) will potentially have impacts.
]]>I wanted to give the ck-kernel a try, and, as indicated in the [repo-ck] wiki page I ran
gcc -c -Q -march=native --help=target | grep march
to see what package is best for me. It says
-march= corei7-avx
which is surprising, because, according to wiki, it corresponds to a Sandy Bridge processor. However my processor is an i7-3517U, which is a mobile dual-core Ivy Bridge processor.
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3517U CPU @ 1.90GHw
Any idea of what it's going on here?
]]>