Slashdot Mirror


Intel's Answer to AMD's Hammer - Yamhill

bdolan writes: "Today's San Jose Mercury News is reporting that Intel is going to put a 64 bit architecture extension in upcoming Pentiums if it turns out the Itanium doesn't take off. Hmm. Apparently they intend to only turn this on if AMD's 64 bit processor make major inroads against the Itanium architecture. Aren't we glad that competition is keeping everyone on their toes."

22 of 544 comments (clear)

  1. Re:The free market at work by Pyromage · · Score: 4, Informative

    It seems your trying to draw a parallel here to the MS case. That is not entirely possible in this instance.

    There is one critical difference: it's possible to clone an x86 processor. They are standard and well documented.

    You can't clone Windows. It is only partially open, with closed file formats and APIs all over the place. Open APIs are often not documented well, or may have undocumented bugs which applications depend on.

    It is possible to make a chip that will run all the same applications as Intel's, and to do so in a reasonable timeframe. However, Wine and LindowsOS are clear counterpoints to that, showing that that CANNOT be done with an OS.

  2. Yamhill by sben · · Score: 5, Informative

    For those who care, Yamhill is a small town WSW of Portland (the little red star at the lower left).

    Fascinating info can be found at cityofyamhill.com, naturally.

    1. Re:Yamhill by Russ+Steffen · · Score: 3, Informative

      Doubtful that Yamhill refers to the town. Every other Intel codename in the last several years has referred to a NW US river (Mendocino, Klamath, Merced, Willamette, Tualatin, Coppermine, etc...). It seems much more probable that Yamhill refers to the Yamhill River.

    2. Re:Yamhill by johnpelster · · Score: 2, Informative

      Yamhill is more than that:

      o It is a river in the Willamette Valley
      o It is a county in Oregon

      Like most Northwestern names, it has Native American roots.

      Prescott, the other code name, was an historical figure in Portland. There is a Prescott Street in North Portland and his picture hangs in the Downtown Central Libarary.

  3. Re:Uhh..naming? by djoham · · Score: 5, Informative

    There actually is a basis for this name. Intel has a large presence in the state of Oregon and has a tendency to give their products code names from that state.

    For example, there's the Willamette (a major river, incidentally one of only a handful in the world that run south to north), the Klamath (a county) and the Deschutes (another county and also a national forrest).

    There may be others, but they don't come to mind at the moment.

    As a former Oregonian, I find this kind of cool...

    Best regards,

    David

  4. Re:Itanium by hpa · · Score: 3, Informative

    Expect it to look a lot like AMD's x86-64 architecture, although it will probably be gratuitously incompatible.

  5. It's called the "Prescott" [Re:Uhh..naming?] by eples · · Score: 2, Informative

    Why do people insist on wasting their moderation points on "funny" comments?!

    The chip is code named Prescott. From the article:

    The Yamhill features are being built into the next version of Intel's Pentium chip, code-named Prescott, with an option to turn the features on or off. In 2003 or 2004, when the Prescott chip is expected to be available, Intel will evaluate AMD's offerings and the success of the Itanium and then decide whether to activate the Yamhill code.

    There you have it.

    --
    I'm a 2000 man.
  6. Re:Multiprocessor? by clem.dickey · · Score: 2, Informative

    IBM's p690 does put 2 processors on a chip.

    But you don't need 2 processors for multiprocessing. "Barrel processors" had one core with multiple contexts (register sets). The contexts would use the execution unit in round-robin fashion. Barrel processors were controlling I/O, where mainframes needed parallelism but not speed. I think CDC PP's and Amdahl channels used them.

  7. Re:The free market at work by dada21 · · Score: 3, Informative

    That's how the free market works: products that are ready for primetime, products that consumers wants, products that offer a price point, will sell.

    Products that are before their time, or cost too much, or don't perform any differently than others (in the consumers' eyes) will not sell.

    What happened to Itanium? The average consumer is very happy with a P2 even today, thank you very much, and probably doesn't need more. Why do we need to see the Itanium succeed in order to prove that the free market works?

    I claim this is proof that the free market works because in 1999, the FTC was seriously considering hurting Intel, and what in the end hurts Intel, causes them to innovate, and causes them to make their products inexpensive is COMPETITION from AMD, not regulation from the FTC. Duh.

    QED...

  8. They do. by rootmonkey · · Score: 2, Informative

    IBM's power4 chip has 4 processing cores on a chip. Intel and Sun have plans in the works. Intel will do this to follow up with the IA-32 Xeon processor. Here is a story on this

    --

    Yes but every time I try to see it your way, I get a headache.
  9. Not exactly by autopr0n · · Score: 4, Informative

    The diffrence between the pentium and the p-pro are rather minute when compared with the diffrence betwee any pentium/486/386/etc chip and the Itanium. To really answer your question, though you kind of have to look at the history of the whole thing.

    To start things off, intel releases the 8086, and the cheaper 8088 (8086 with a 8, rather then 16 bit bus interface). And thus begins the x86 era.

    A little later intel decides they need a 32 bit CPU, but rather then design a totaly new chip, they just add a bunch of extensions to the 16 bit one. They call this new chip the 386, and it's supposed to revolutionize everything. The chip is totaly backwards compatable with the old 8086's and 286s (so the old register AX becomes EAX, but you can still access the first half as AX).

    for a long time (windows 3.1) most software still ran in 16 bit mode, not really utilizing the software. IIRC It wasn't untill windows95 and NT started getting used that people really started to take the full potential of their machines in every day tasks.

    Now, this is also around the time of the Pentium and the Pentium pro. The pentium ran both 32 and 16 bit software quickly, but the ppro ran 32 bit software faster, and 16 bit software more slowly (of course, the p-pro core became the pentium II, then the pentium III and ran at much higher clockspeeds, so it eventualy became a non issue, a 1.3ghz pIII is going to crunch 16 code faster then a pentium233mmx no mater what :P)

    Now, when you look at what AMD is doing and I guess intel now with their rather odly named Yamhill is taking the orgional design and adding 64bit extensions the way they added 32 bit extensions to the 286. EAX becomes RAX, and you can get at the first half by calling it EAX and the first quarter by calling AX, etc.

    Itanium is a totaly diffrent thing, it's a whole new system with x86 support tacked on extra, rather then tacking on 64 bit support to an aging archetecture.

    Hrm, I hope that explains things.

    --
    autopr0n is like, down and stuff.
    1. Re:Not exactly by tempmpi · · Score: 4, Informative

      You are right: the p-pro core became the pentium II.
      But the PII doesn't suck at 16-bit code because Intel done some little changes in the p-core so that the PII could crunch 16-bit code much faster. In fact there was only one problem with p-pro core design that caused the p-pro to suck at 16-bit code. The p-pro misses the segment register caches, that were included in the pentium and reincluded in the pII. Because of that 16-Bit programms that use segments will generate one additional memory access for every memory access they were doing. When Intel saw that that there was a need to run 16-bit programms they reincluded this caches and because that the performance of the pII doesn't suffer anymore from 16bit code.

      There is also something important to note on AMDs x86-64 extensions. On the integer side they are really compareable to the 32-Bit extensions made in the 386 but the x86-64 extensions also change the working of the floating point unit.

      All current x86 CPUs could reach very good benchmark scores on benchmarks that work mostly with integer numbers but they get bad scores at many benchmarks that use floating point numbers a lot. Intel and AMD are already trying hard to make their FPUs faster, but they couldn't reach really good improvements because the x86 fpu intestruction set isn't good for modern cpus. The x86 fpu doesn't have a normal register set with registers that could be addressed individually but it uses an register stack. You could only address the top of the stack(TOS), the register under the TOS,TOS-2 and so on. If you used a RPN calculator, you know what i'm talking about. This design isn't that bad if you execute one instruction at a time. It even makes programming fpu asm a bit easier.

      The problems came with the introduction of cpu that executes more than one instruction at a time. To make full use of that feature the compiler or assembler programmer must often interleave multiple calculations. The fpu stack is very hostile against such optimizitions.

      Because of that AMD has done a almost complete rework of the x86 fpu instruction set that matches the internal working of moderne fpus much more.

      --
      Jan
  10. Re:Multiprocessor? by Steveftoth · · Score: 3, Informative

    Yes its called Superscaler.

    Basically, every intel chip since the pentuim has had more then one 'execution' unit. The original pentuim had 2, but the second one was crippled.

    The Pentium 2 was the first full superscalar intel chip. Now they throw all the 486 away though, as they take the instructions and turn them into many micro instructions, then have another internal execution engine that executes the new instructions, then reassembles them at the end. Why? because the x86 instruction set is too complex to build a processor that can handle all instructions in HW alone. So they turn the large instruction into many small ones. Then they have a core that is very superscalar and can execute the micro instructions very fast.

  11. Jackson by volpe · · Score: 3, Informative

    How is what you're suggesting different from Hyper-Threading or "Jackson" technology?

  12. Re:64-bit by Courageous · · Score: 3, Informative

    What's the point of adding more bits?

    The absolute amount of memory which can be addressed in 32 bits, sans tricks, is 4GB. That's combined memory and swap. Quite a few people care about that kind of thing, namely just about anyone who runs any decent sized server.

    Further, consider the rate at which system memory has been increasing, and project it a few years. If it continues, and I realize that maybe it won't, there's a problem.

    C//

  13. Re:The free market at work by Ryan+Amos · · Score: 3, Informative

    Microsoft is a monopoly because they own 95% of the desktop operating system market. Essentially, if software companies want to sell anything, they have to make it for Windows. And if businesses want to be able to use off-the-shelf software, all their employees, clients and vendors use Windows, so they must as well. It's a total catch-22.

    Microsoft also operates in many different areas of the computer industry. Almost all of them, in fact. And the fact that they own the operating system means that they get to plaster Windows with "Buy MS Office!" and "Use MSN!" messages. And now, everyone uses MS Office, so it's the same problem. There has to be some standard interface between companies, and file formats have to be compatible and work *exactly as they are expected to*. Thus, people use Windows and MS Office.

    Also, have you looked at Microsoft's pricing lately? I'm currently in college, and MS has some incredible discounts (as in $5 for Office, though this is also to train an entire generation to use their software, so the businesses that hire them will use it as well;) but Windows 2000 was something on the order of $300, Office is about the same. They really can charge whatever they want, and people will pay it, but they keep pricing at these levels so that they can defend themselves as "reasonable" in court.

    Microsoft does have many competitors. Many small ones. If someone tried to develop an office suite comparable to MS Office, Microsoft would just buy the company for an insane amount of money. They're so big, they can crush the smaller players. They're having some trouble with Sony in the console wars, but only because Sony uses many of these same tactics (VGS and Connectix ring any bells?)

    Intel never really had quite the monopoly Microsoft had. AMD/Cyrix/VIA have always been there, just not as a large presence, but large enough that Intel couldn't sweep them away. Intel just got unlucky actually, AMD decided to make a strong push on an existing market as Intel was trying to force a major (and expensive) technological change down the consumers' throats (RDRAM.)

    And AMD's success is also largely due to consolidation within the marketplace. When Compaq bought Digital, most of the Alpha engineers bailed and went to AMD. The Alpha was an extremely advanced chip, so they brought their experience with them to AMD and helped design the Athlon, which was finally a product which could challenge Intel for real (they had been a major player in the budget market for years with the K6 series.) The Athlon is not just a "fight the man" sort of thing, it really is a good piece of engineering at a fair price.

  14. Re:This article is alarming, but poorly written. by Anonymous Coward · · Score: 1, Informative

    All RISC really means anymore is that the microarchitecture is a load/store one. That is, you can't do an op like this:

    add.w (a0)+, d0

    Instead, your ALU ops have to be in regs first.

  15. Re:The free market at work [My response is OT] by subgeek · · Score: 2, Informative

    not to start a flame war, but i have been reading your posts and feel a need to speak up. also, i am probably way off topic.

    i am all for competition and think people should try to make a better product. but it seems that the only reason you are willing to accept for why a monopoly might exist is that they make better stuff. companies have made products that were as good as or better than windows.

    take Be. they made BeOS, which people still use even though it is dead. microsoft crushed it as it was just getting off the ground. they didn't just out-design Be, they told their vendors that they were not allowed to sell computers that did not also contain windows. microsoft also required them to diable BeOS by default. i fail to see how that makes windows a superior product. maybe it didn't have all of the features of windows, but operating systems to take time to develop. if they are stamped out in their infancy all of the innovation they might have had is lost. things like this also serve as a warning to others who would enter microsoft's turf. apple and the smorgasbord of *nixes survive because they are in different markets.

    they innovate to the extent that you will be enticed into upgrading. make it cheaper in the short run to win in the long run.

    --
    you probably shouldn't have read this.
  16. Re:Uhh..naming? by wildwood · · Score: 2, Informative
    As a former native, let me add to the list of All Things Klamath:
    • Klamath Falls (the falls no longer exist, but the city's still named that)
    • Klamath Basin
    • Klamath indian tribe (and language)


    That's it. I'm done.
    --
    normal(adj)- people who don't sit on slashdot all day wondering why everyone else isn't building robots [DECS]
  17. Re:Uhh..naming? by ByteHog · · Score: 2, Informative

    The Columbia river in Washington runs North, East, West AND South. Depending of course on which part of the river you look at.

    --
    - This isn't the sig you're looking for. Move along, move along..
  18. Re:"8086 took 3 weeks to design"-easy to believe! by Detritus · · Score: 4, Informative

    I think it is very unlikely that the 8086 was designed in three weeks. I used to have a book on the 8086, written by the chip's architects.For what the chip was designed to do, they did a good job. Intel thought that most of the software for the chip would be written in PL/M or Pascal. The segmented architecture was a good match to those languages. The floating point hardware (8087) was a major advance, being the predecessor of IEEE floating point. 8080 programs could be mechanically translated into 8086 programs. The 8086 supported all of the peripheral chips that had been designed for the 8080.

    --
    Mea navis aericumbens anguillis abundat
  19. Re:"8086 took 3 weeks to design"-easy to believe! by Anonymous Coward · · Score: 1, Informative
    Note that the article is wrong about the i432, which was announced well after the 8086 and about at the same time as the 80286. What Intel never had in mind was to follow-on together with the at the time called iAPX86 series for 2 decades. The clear path to succession was the iAPX432 with large address spaces and a funky architecture. In some respects, Itanium is starting to look like the heir of the iAPX432.

    However, what is true is that the architecture, instruction set and so on of the 8086 was designed in only a few weeks leaving even the design of the x87 for later...when the engineers discovered that not enough opcodes had been left for a 2 register address machine and inflicting the awful register stack architecture to the rest of the world.

    The final, off-topic question, is why IBM chose Intel (and M$) for the PC when much better designs (68000 for example) were available. There are seevral reasons to it: there was at the time no 8 bit version of the 68000 and this would have made the motherboard more costly, the 68000 with its non multiplexed bus in a 64 pin DIL package was coslty, and finally some claim that IBM thought that the chip was so awkward that it could never be extended past the toy level to compete with their bread and butter mini and mainframes.