| View previous topic :: View next topic |
| Author |
Message |
nabla²
Apprentice
Joined: 17 May 2005
Posts: 280
|
 Posted: Mon May 23, 2011 5:52 pm Post subject: Intel core2duo (amd64) -> Intel i7 sandy bridge (amd64)? |
 |
|
Hi,
I plan to upgrade my hardware. ATM, I use a Intel core2duo on a p35 board using amd64 profile. Can I use this install for a new system based in intel i7 (sandy bridge) on a p67 board?
Of course, new kernel modules. And yeah, new gcc settings, but in principle it should boot, right? So I can work on the changes while having a working system?
Any further advice?
Cheers
_________________
Gentoo on Intel Core Duo 2 E6750, Gigabyte P35-DS3P, NVIDIA 8800GTS (amd64) |
|
| Back to top |
|
 |
DaggyStyle
Watchman
Joined: 22 Mar 2006
Posts: 5910
|
| Posted: Mon May 23, 2011 8:03 pm Post subject: |
|
|
just switch to -march=native if you didn't, make sure that all the right stuff for the new hardware is compiled in the kernel, reboot and run emerge -e world.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
| Back to top |
|
|
Aquous
l33t
Joined: 08 Jan 2011
Posts: 700
|
| Posted: Tue May 24, 2011 7:22 am Post subject: |
|
|
| Since there are no features in the Core2 series that are not supported by Sandby Bridge, the system will boot just fine. (You just won't get maximum performance because Sandy Bridge offers new goodies such as AVX which haven't been compiled into the Core2-optimized binaries.) |
|
| Back to top |
|
|
DaggyStyle
Watchman
Joined: 22 Mar 2006
Posts: 5910
|
| Posted: Tue May 24, 2011 6:54 pm Post subject: |
|
|
| Aquous wrote: | | Since there are no features in the Core2 series that are not supported by Sandby Bridge, the system will boot just fine. (You just won't get maximum performance because Sandy Bridge offers new goodies such as AVX which haven't been compiled into the Core2-optimized binaries.) |
AVX support is part of gcc-4.6.0 afaik, when gcc will support it, all he will need to do i reemerge relevant packages without touching the conf files.
also, native gives better results, see your current flags and what native gives you.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
| Back to top |
|
|
Shining Arcanine
Veteran
Joined: 24 Sep 2009
Posts: 1110
|
| Posted: Tue May 24, 2011 11:00 pm Post subject: |
|
|
| Aquous wrote: | | Since there are no features in the Core2 series that are not supported by Sandby Bridge, the system will boot just fine. (You just won't get maximum performance because Sandy Bridge offers new goodies such as AVX which haven't been compiled into the Core2-optimized binaries.) |
A great deal of the stuff people do in general does not benefit from vector instructions. AVX will not make things much faster. It will mainly help on things like video decompression assuming that GPU acceleration is not available.
Anyway, he can find out what -march=native does by running gcc -march=native -Q -v --help=target.
Here is the output from one of my systems:
| Code: | # gcc -march=native -Q -v --help=target
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with: /var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.4.5 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.4.5 --mandir=/usr'
Thread model: posix
gcc version 4.4.5 (Gentoo 4.4.5 p1.2, pie-0.4.5)
COLLECT_GCC_OPTIONS= '-Q' '-v' '-fhelp=target'
/usr/libexec/gcc/x86_64-pc-linux-gnu/4.4.5/cc1 -v help-dummy -D_FORTIFY_SOURCE=2 -march=core2 -mcx16 -msahf -msse4.1 --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=6144 -mtune=core2 -dumpbase help-dummy -auxbase help-dummy -version -fhelp=s
The following options are target specific:
-m128bit-long-double [disabled]
-m32 [disabled]
-m3dnow [disabled]
-m3dnowa [disabled]
-m64 [enabled]
-m80387 [enabled]
-m96bit-long-double [enabled]
-mabm [disabled]
-maccumulate-outgoing-args [disabled]
-maes [disabled]
-malign-double [disabled]
-malign-functions=
-malign-jumps=
-malign-loops=
-malign-stringops [enabled]
-march= core2
-masm=
-mavx [disabled]
-mbranch-cost=
-mcld [disabled]
-mcmodel=
-mcx16 [enabled]
-mfancy-math-387 [enabled]
-mfma [disabled]
-mforce-drap [disabled]
-mfp-ret-in-387 [enabled]
-mfpmath=
-mfused-madd [enabled]
-mglibc [enabled]
-mhard-float [enabled]
-mieee-fp [enabled]
-mincoming-stack-boundary=
-minline-all-stringops [disabled]
-minline-stringops-dynamically [disabled]
-mintel-syntax [disabled]
-mlarge-data-threshold=
-mmmx [disabled]
-mms-bitfields [disabled]
-mno-align-stringops [disabled]
-mno-fancy-math-387 [disabled]
-mno-fused-madd [disabled]
-mno-push-args [disabled]
-mno-red-zone [disabled]
-mno-sse4 [disabled]
-momit-leaf-frame-pointer [disabled]
-mpc
-mpclmul [disabled]
-mpopcnt [disabled]
-mpreferred-stack-boundary=
-mpush-args [enabled]
-mrecip [disabled]
-mred-zone [enabled]
-mregparm=
-mrtd [disabled]
-msahf [enabled]
-msoft-float [disabled]
-msse [enabled]
-msse2 [enabled]
-msse2avx [disabled]
-msse3 [enabled]
-msse4 [disabled]
-msse4.1 [enabled]
-msse4.2 [disabled]
-msse4a [disabled]
-msse5 [disabled]
-msseregparm [disabled]
-mssse3 [enabled]
-mstack-arg-probe [disabled]
-mstackrealign [enabled]
-mstringop-strategy=
-mtls-dialect=
-mtls-direct-seg-refs [enabled]
-mtune= core2
-muclibc [disabled]
-mveclibabi=
COLLECT_GCC_OPTIONS= '-Q' '-v' '-fhelp=target'
/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/../../../../x86_64-pc-linux-gnu/bin/as -V -Qy -o /tmp/cc8nE7w4.o /tmp/ccqII9tE.s
GNU assembler version 2.21 (x86_64-pc-linux-gnu) using BFD version (GNU Binutils) 2.21 |
In this example, the relevant information is "-march=core2 -mcx16 -msahf -msse4.1 --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=6144 -mtune=core2". |
|
| Back to top |
|
|
|
Other Things Gentoo
