| 1 |
Am 2011-11-18 01:04, schrieb Neil Bothwick: |
| 2 |
> On Thu, 17 Nov 2011 23:13:31 +0100, Stefan G. Weichinger wrote: |
| 3 |
> |
| 4 |
>> Right now I have everything built with rather CPU-specific |
| 5 |
>> CFLAGS. |
| 6 |
>> |
| 7 |
>> Specific L1/L2-cache-sizes and stuff, set after doing something |
| 8 |
>> like "gcc -Q --help=target -march=native" .... (gentoo wiki). |
| 9 |
>> |
| 10 |
>> I wonder if this C2D-E6600-specific stuff would boot on the |
| 11 |
>> i7-2600k? Yeah, I could just try it. |
| 12 |
>> |
| 13 |
>> But maybe I should do something to prepare that migration? |
| 14 |
> |
| 15 |
> I did a new installation as the old one had started life on an |
| 16 |
> Athlon64 about 8 years ago and then migrated to the C2D. But it |
| 17 |
> will probably work as long as you kernel included support for both |
| 18 |
> types of hardware. |
| 19 |
> |
| 20 |
> If you're feeling adventurous, GCC 4.6, currently masked for |
| 21 |
> testing, has specific -march options for the i7 and Sandybridge i7, |
| 22 |
> according to the Gentoo Wiki CFLAGS page. |
| 23 |
> |
| 24 |
> Using 4.5.3 and -march=native, I had a couple of showstopping |
| 25 |
> build failures, that were fixed by switching to -march=core2 |
| 26 |
> -mtune=generic. |
| 27 |
|
| 28 |
Thanks a lot. Will try. hardware order planned for next week maybe. |
Archives