I don't think the new cpu will be a problem. You may not get specific optimizations right away but i686 should work. However the new cpu will come with new chipset, so you might have problems with your motherboard.slackeast wrote:I'm currently building a new pc that will use the new intel core 2 duo processor.
is it reasonable to expect to get gentoo working on the machine once I get the computer up? I was thinking there might be issues because its a new processor. I also noticed that there is separate downloads for amd64 architecture, does gentoo expect to do the same for intel 64 bit?
thanks.
So there should be no problem.Unfortunately, we do not have our Intel Core 2 Duo Conroe Linux numbers to share for this midnight primer, but we intend to have up some performance numbers in the very near future. When it comes to the GNU/Linux compatibility with these new Core 2 Duo components, there really should not be anything out of the ordinary. The NVIDIA nForce 500 AMD series run fine with the needed open-source modules under Linux on recent kernels, and the NVIDIA nForce 500 Intel Chipsets should offer the same compatibility. More on the compatibility information will come once we have completed all of our testing.



No, I believe AMD64 and EM64T are compatible. So you should be using amd64 stages on a 64-bit Core 2.Paapaa wrote:Please, let's not make this a fanboy thread. Copying has been done so many times (by both sides) that this shouldn't make any difference. Gentoo shouldn't favor AMD over Intel or Intel over AMD and this is why I asked. Especially:
4. Is there anything AMD specific in AMD64 stage3 or does is also work with EM64T?
5. Is there anything AMD specific in the keyword amd64 or do the packages also work with EM64T?
As far as I remember amd64 and EM64T are not fully compatible, there's few instructions that differ. But gentoo's stages should work with both. But if you then change generic 64 cflag to opteron64 example, then it won't work with EM64T.Archangel1 wrote:No, I believe AMD64 and EM64T are compatible. So you should be using amd64 stages on a 64-bit Core 2.Paapaa wrote:Please, let's not make this a fanboy thread. Copying has been done so many times (by both sides) that this shouldn't make any difference. Gentoo shouldn't favor AMD over Intel or Intel over AMD and this is why I asked. Especially:
4. Is there anything AMD specific in AMD64 stage3 or does is also work with EM64T?
5. Is there anything AMD specific in the keyword amd64 or do the packages also work with EM64T?
As far as I know the name 'amd64' was chosen because AMD brought out a 64-bit superset of x86, and at the time there weren't any Intel chips using it. It had to be called something, and amd64 is less awkward to type than x86_64
For a 64 bit system, yes. For a 32 bit system it would be i686-pc-linux-gnuPaapaa wrote:2. What CHOST to use? Is "x86_64-pc-linux-gnu" the one?
See above.3. Which stage3 tarball is the correct? i686 or AMD64?
They won't be renamed. There is no benefit in doing that, but it would cause an enormous amount of trouble.If AMD64, then the stage and keywords should be immediately renamed as they don't reflect the reality.

I'm considering a Pentium D 805, which supports EM64T. If the 3Dnow! extensions are the only difference, would it be possible to set "-march=athlon64 -mno-3dnow"? And if so, is it worth doing? Or am I completely off base here?tkdfighter wrote:AMD64 and EM64T are compatible with each other. The only reason why you should use -march=nocona on a Core 2 is because -march=[k8,opteron,amd64,...] sets the 3Dnow! Cflag, which Intel does not support. See the GCC i386 and x86_64 options manual for more details.
I also hope for all you Core 2 owners that the GCC devs will make a Core2 option, because Nocona is a Pentium 4, which is based on the Netburst architecture.
Is the Pentium D not a Nocona core? Why not just use that instead of athlon64?nonotme wrote:I'm considering a Pentium D 805, which supports EM64T. If the 3Dnow! extensions are the only difference, would it be possible to set "-march=athlon64 -mno-3dnow"? And if so, is it worth doing? Or am I completely off base here?
Why would you want to? Pentium D's use nocona.nonotme wrote:I'm considering a Pentium D 805, which supports EM64T. If the 3Dnow! extensions are the only difference, would it be possible to set "-march=athlon64 -mno-3dnow"? And if so, is it worth doing? Or am I completely off base here?tkdfighter wrote:AMD64 and EM64T are compatible with each other. The only reason why you should use -march=nocona on a Core 2 is because -march=[k8,opteron,amd64,...] sets the 3Dnow! Cflag, which Intel does not support. See the GCC i386 and x86_64 options manual for more details.
I also hope for all you Core 2 owners that the GCC devs will make a Core2 option, because Nocona is a Pentium 4, which is based on the Netburst architecture.
