Slashdot Mirror


Intel Quietly Adopts AMD's x86-64

HishamMuhammad writes "The rumors reported earlier at /. are confirmed. The latest offerings in the Pentium 4 family now support AMD's x86-64 architecture, even though Intel is not willing to admit it very openly, by using cryptic names like EM64T and (gasp) IA-32e. (The naming issue was discussed on lkml, and the consensus there was to use 'x86-64,' even though sometimes AMD refers to it as 'AMD64'). Intel's FAQ admits their implementation is basically compatible with x86-64, except for the minor differences that have always set Athlons and P4s apart. It's about time Intel jumped on AMD's bandwagon, since its homegrown 64-bit architecture seems not to be doing very well."

16 of 392 comments (clear)

  1. AMD Better Get Its Act Together by darkmeridian · · Score: 4, Insightful

    Sure, AMD is ahead right now. There is incompatibility between the two 64 bit architectures, and developers may choose to design for one or the other. But the Intel FAQ is right in that Intel processors support SSE3 and HyperThreading, for which AMD has no counterpart. This is in addition to Intel performance-enhancing compilers. If developers choose to develop around Intel's 64 Bit processor, then AMD may soon find itself behind again.

    --
    A NYC lawyer blogs. http://www.chuangblog.com/
    1. Re:AMD Better Get Its Act Together by Slack3r78 · · Score: 3, Insightful

      I'd just like to add on to this that the reason the Athlons and P-M's don't need Hyperthreading is that HT is essentially a latency hiding method to make up for the obscenely long Netburst pipeline. Basically, keeping the 30-stage pipeline full is difficult with a single thread, so allowing the processor to address multiple threads at the same time helps keep the pipeline full. I'd suggest reading Hannibal's excellent articles at Ars Technica if you wish to learn more on the subject.

      Essentially, I've always felt that HT is more of a marketing gimmick than it is some new revolution in computing. While it might help performance some, AMD's upcoming dual core chips will do far more to help performance as it actually *is* a multiprocessor system rather than faking it like HT. Remember, K8 was designed with multicore in mind from the start, with Netburst, it's been hacked in.

  2. Re:Just as a side note by Erik+Hensema · · Score: 3, Insightful

    A nice and confusing name apparently only chosen because the debian developers don't like intel for what they did (namely copying the amd64 and forgetting to mention that fact in their press releases).

    I prefer the nice vendor-neutral x86-64.

    --

    This is your sig. There are thousands more, but this one is yours.

  3. Quietly? by stratjakt · · Score: 3, Insightful

    Intel's been talking about this for some time, and it's been posted on /. numerous occasions.

    I guess we're trying to paint them with a bad brush, just because. I don't see anything quiet about it.

    Do you mean quiet as in they aren't saturating the market with bullshit about how much more amazing the internet will be with 64 bit extensions and other nonsense claims designed to sucker the technically illiterate into upgrading for no reason?

    --
    I don't need no instructions to know how to rock!!!!
  4. Re:Sound fine and all... But.. by gehel · · Score: 5, Insightful

    The question is not if it perform better for the same clock speed. The real question is to compare performance/price or performance/power consumption.

  5. Re:FYI by forkazoo · · Score: 4, Insightful

    The complete architecture reference manual was available for free, including shipping, by requesting it from AMD's website. I doubt they needed to do much reverse engineering.

  6. Intel should know better... by IGnatius+T+Foobar · · Score: 3, Insightful

    One would think that Intel, better than anyone else, should know one simple fact about the computer universe:

    Try as you might, you just can't get rid of x86.

    RISC vendors failed. Intel's own RISC efforts failed. Itanium is an overengineered design that nobody wants. What did they think was going to happen?

    In the world of computers, especially PC type computers, backwards compatibility is king. That's what keeps incumbents like Intel and (especially) Microsoft on top. You'd think they'd know this better than anyone else. Has AMD beaten Intel at its own game? Time will tell.

    Look on the bright side: the complete failure of Itanium in the marketplace (let's call it what it is, even though Intel hasn't officially thrown in the towel yet) means that we won't be stuck with an entire generation of computing where Intel calls the shots. Can you imagine what would have happened if Itanium prevailed and nobody else was allowed to produce a compatible processor?

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
  7. rubber meets the road by Doc+Ruby · · Score: 3, Insightful

    Where would the car industry, and the American economy, be if we had headlines like "GM Quietly Adopts Ford's Gascap Diameter"? These interoperability issues might make short-term profits for Intel, and offer marketdroid simplified lockin strategies, but they're inefficient limits to scaling the market to encompass everyone. So longterm profits are sacrificed, as well as usability. This fruit of the Intel/AMD crosslicense agreements should be congratulated and promoted as a "best practice" that's best for everyone touched by the industry - which is practically everyone.

    --

    --
    make install -not war

  8. Re:Struggling Intel by Glock27 · · Score: 4, Insightful
    Still, AMD market cap (~8B) is dwarfed by Intel's (~150B).

    Which does make one wonder how Intel is squandering all that R&D money. The one good investment appears to be the Israeli design team, which did the Pentium-M (essentially a slightly reworked PIII design). Otherwise, every one of Intel's major efforts (with the possible exception of wireless chipsets) has been subpar for the last couple of years.

    AMD64 is simply better at the present time, especially when you look at the SMP and multicore story.

    The stock performance of the two companies (as opposed to the market cap) certainly reflects those facts! :-)

    --
    Galileo: "The Earth revolves around the Sun!"
    Score: -1 100% Flamebait
  9. Re:Sound fine and all... But.. by ArbitraryConstant · · Score: 3, Insightful

    Intel performs better with media encoding stuff, AMD performs better on other things.

    Like code with branches, and code that accesses memory.

    --
    I rarely criticize things I don't care about.
  10. Meaningless Indication of Processor Speed by DragonHawk · · Score: 5, Insightful

    "How will it perform compared to AMD's chips? AFAIK AMD usually performs better clock to clock?"

    Comparing processors "clock for clock" has never meant a lot, and is meaning less and less all the time. Different designs do things so differently that clock rate has about as much to do with actual performance as the color of the chip package.

    The best measure of CPU performance remains the price/performance ratio. That is, for a given amount of money, how fast will a CPU perform a given task? In other words, how much bang for the buck. AMD has consistantly been beating Intel in that department for years. Sure, you might find a chip from Intel that is 10% faster, but it will cost you 80% more.

    Even comparing price/performance on just CPUs has become difficult to impossible. Core logic (especially the memory subsystem and periperal bus) have become so important, and so differentiated, that establishing an apples-to-apples CPU comparison is hard. So instead of comparing just CPUs, you have to compare CPU/chipset/memory combinations.

    --

    dragonhawk@iname.microsoft.com
    I do not like Microsoft. Remove them from my email address.
  11. Re:Just as a side note by hawkbug · · Score: 3, Insightful

    Wow, wish I had mod points - that's extremely informative. That explains the retarded names from Intel and AMD ever since then. Such examples of horrible names - Athlon XP, Centrino, etc. I prefer 1.4 GHZ 686 myself. You know exactly what you're getting then, same goes for the stupid PR numbers.

  12. Re:HyperThreading != Dual Core chips by Carewolf · · Score: 3, Insightful

    Exactly two cores on a single die is _better_ than SMT(aka. HyperThreading).

    In theory it is also more expensive to produce, but with the K7/K8 design, implementing a multicore cpu is just so much less R&D than implementing HyperThreading, that AMD might easily sell multicore-CPUs in direct competion with Intel HT chips.

  13. Comment removed by account_deleted · · Score: 4, Insightful

    Comment removed based on user account deletion

  14. Re:Just as a side note by bob+beta · · Score: 3, Insightful

    Intel was too set in their old ways to put any kind of fight.

    Wow. What an ironic assertion. Intel goes out of their way to produce a new 64-bit architecture, and AMD, clinging to the old instruction set, puts out a bolt-on 64-bit kludge in response.

    Because a bunch of old farts want to 'stay the course' the kludge solution is perceived as 'more successful' (in the short term). As a result, you accuse Intel of being 'set in their old ways.'

    That's amazing, ya know.

  15. Re:Just as a side note by Vancorps · · Score: 3, Insightful
    You present more or less truth in that the assertion is indeed ironic, but your portrayal of x86-64 is shortsighted at best. It is not a bolt on to the 32bit instruction set. AMD went in and cleaned out as much legacy crap as they could and then proceeded to scale it out.

    Yes the IA64 route was all new but it presented adopters with no options. The Alpha processors are still the best but they aren't successful because there's no interest in rewriting the billions of lines of code that is out there to fit the platform.

    That said, x86-64 is not a short term solution, it will work in the long term evolving much like i386 did. The world moved from 8088 to 80286 without a problem for a reason. This method is proven successful and why Intel abandoned it is beyond me. It doesn't help when you design a brand new incompatible instruction set that isn't any faster either.