Slashdot Mirror


Intel Dumps Iitanium's x86 Hardware Compatibility

Spinlock_1977 writes "C|Net is running a story that Intel is going back to software x86 emulation on Itanium in order to reclaim chip real estate. (room for another 9MB of cache?) One notable quote about x86 emulation: 'Basically, no one ever used hardware-based IA-32 execution, so better to use the silicon for something else,' said Illuminata analyst Gordon Haff. 'Of course, basically no one uses software-based emulation either, but at least that doesn't cost chip real estate.'"

277 comments

  1. Better use for sillicon? by Anonymous Coward · · Score: 5, Funny

    Intel's chips will use that extra sillicon for a nice pair of fake breasts. That's sure to up their earnings next quarter. Take that AMD.

    1. Re:Better use for sillicon? by PCeye · · Score: 2, Informative

      Fake breasts are of silicone...unless you have a thing for bots

      Oblig. Futurama ref: "Hey there sailing unit!"

    2. Re:Better use for sillicon? by Leroy_Brown242 · · Score: 1

      I like fake tits to jiggle a bit. Silicon is a bit hard, like cuddling with bowling balls. :)

    3. Re:Better use for sillicon? by gmby · · Score: 1

      Intel's chips will use that extra sillicon for a nice pair of fake breasts.

      I think you misspelled "chicks".

      --
      I don't want a pickle; I just want a Motor-Cycle! A four foot cop arrived with a five foot gun!
    4. Re:Better use for sillicon? by pegr · · Score: 1

      >> Intel's chips will use that extra sillicon for a nice pair of fake breasts.

      >I think you misspelled "chicks".

      Yeah, well at least he didn't misspell the name of the chip in question in the headline of the story...

    5. Re:Better use for sillicon? by grahamlee · · Score: 1

      That wasn't a misspelling; they're now called iItanium because they're going to be used in the Xserve.

  2. Shouldn't matter with modern software. by Anonymous Coward · · Score: 5, Interesting
    Seems most of the better software today either falls into 2 camps:
    • Software with source available; so "configure; make; make test; make install" will work, and
    • Virtual machine based stuff (Java/JVM, .NET/CLR) (even popular on cell phones these days)

    I think the days of it mattering what the exact instruction set is are pretty much over.
    1. Re:Shouldn't matter with modern software. by Eightyford · · Score: 5, Funny

      Virtual machine based stuff (Java/JVM, .NET/CLR) (even popular on cell phones these days)

      So that's why it takes two friggen minutes to turn on my cell phone!

    2. Re:Shouldn't matter with modern software. by Eightyford · · Score: 4, Funny

      Flamebait huh? There must have been a Java programmer with mod points.

    3. Re:Shouldn't matter with modern software. by bobcat7677 · · Score: 5, Funny

      Now I understand! That little coffee cup symbol that comes up on my phone is really telling me to go have a cup of coffee while I wait for the Java software to start. And all along I thought it was not functional at all but just an amusing little pun on the "Java" name... Silly me.

    4. Re:Shouldn't matter with modern software. by springbox · · Score: 1

      You missed precompiled binaries targeted for a certain architecture. None of the software I use on my computers runs off of a VM. It's either precompiled or bulit from the source. So yes, I would say it matters because I make it a point to avoid most things that use VMs.

    5. Re:Shouldn't matter with modern software. by po8 · · Score: 2, Insightful

      Still doesn't matter, because in 2006 recompiling a program with a native-code compiler targeted to a random ISA (for a given operating system) is practically free—especially if the program was written in a reasonable modern language.

      If the Java VM is your beef, check out gcj. Sure, it still has a runtime system. But its performance overhead relative to compiled C code is almost always negligible or better.

    6. Re:Shouldn't matter with modern software. by jaywarrietto · · Score: 0, Interesting

      not all java programmers would've modded you down for that. at least there would've been one less. I thought it was quite funny. not much exaggeration from the truth. people with mod points should read more carefully than they do. I've had bad karma for at least a year because of one post that someone thought was a flame. becasue of that I've not had mod points or the chance to metamoderate since then.

    7. Re:Shouldn't matter with modern software. by Anonymous Coward · · Score: 0

      Sorry, but not all open source developers are retarded enough to use auto*hell. Some of us still can write portable code and can write proper makefiles that don't depend on mountains of GNU/Crap.

      So, make; make install; should be more than enough(unless your system is really retarded and you might need to edit a line or two in conf.mk, which anyway is much easier than figuring out how to coerce auto*hell with --hideously-long-options to do what you are telling it to do)

    8. Re:Shouldn't matter with modern software. by chris_eineke · · Score: 5, Funny

      You mean 'a Java programmer with a collection of instances of class ModPoint'. ;)

      --
      "All you have to do is be fragile and grateful. So stay the underdog." Chuck Palahniuk, Choke
    9. Re:Shouldn't matter with modern software. by Edmund+Blackadder · · Score: 2, Insightful

      As somebody that's trying to run a 64 bit linux installation, I must tell you that this software nirvana where the instruction set does not matter is far far away.

    10. Re:Shouldn't matter with modern software. by linuxfanatic1024 · · Score: 1

      Well, I don't use the autotools for my software. However, that's not my point.

      I like running ./configure because it makes sure I have the required libraries and dev files to compile the program. There are some programs I have to use --really-really-long-option things with, but I can copy and paste with the mouse from the --help screen. Yes, even console junkies can do it with GPM. Anyway, ./configure saves the headaches from wondering why a program refuses to compile by checking first.

      --
      Microsoft-free since March 28, 2004
    11. Re:Shouldn't matter with modern software. by lateralus_1024 · · Score: 1

      "So that's why it takes two friggen minutes to turn on my cell phone!"

      Well that instance of the DigCam class isn't going to destruct by itself. You should look into upgrading your phone, your phone's GC() could be optimized with a simple firmware update.

      --
      If you think /. comments are bad, check out Digg.
    12. Re:Shouldn't matter with modern software. by Julian+Morrison · · Score: 1

      Nah, the reason it takes two minutes is because the Java's running on a chip that would be underpowered for an early 90s game console. And it's doing that in order to give you a battery life counted in hours, not minutes.

      When somebody invents a good battery, Java will be fast on cell phones, too.

    13. Re:Shouldn't matter with modern software. by aaronl · · Score: 2, Interesting

      Yeah, no kidding, and the worst offenders are these wonderful things that everyone tauts as the fix to the problem: the web browser, and assorted plugins, and Java. The next biggest is video codecs, courtesy of the Windows people that can't seem to understand why it's nice to be able to play back that precious content if they want you to buy it.

      I tried to run 64 bit Linux with Ubuntu. It wasn't worth it. I spent a week screwing around with it and trying to be able to just reliably play a video, or to even start a something that was written in Java. I formatted and went back to 32 bit Ubuntu. It's no picnic trying to do the same with Windows, either; very similar problems.

    14. Re:Shouldn't matter with modern software. by Z34107 · · Score: 1

      I think the days of it mattering what the exact instruction set is are pretty much over.

      Wrong. As you say, virtual-machine-esque stuff defines standard bytecodes for all platforms. However, I don't see a Java-based processor anywhere. Somewhere along the line, the high-level VM instructions must be converted to the native CPU instruction set, which actually runs the program.

      As long as computers have CPUs, the instruction set will matter, as every program - VM or not - will have to use them.

      --
      DATABASE WOW WOW
    15. Re:Shouldn't matter with modern software. by Hurricane78 · · Score: 5, Informative

      I'm sorry, but this is plainly wrong!

      The CPUs of a modern mobile phone are the same that are in modern gameboys: ARM9 (or sometimes lower)
      The only difference are the added chips for multimeda and other stuff in gameboys.

      As someone who actually *wrote* a game engine and other apps for mobile phones in java i can tell you that it IS java's fault!
      The best proof is that apps compiled directly for the chip run at least three times faster without doing anything better.
      So it can't be the chip.
      Even with the libs of the phone manufacturer it does not become much better, because additionally to still bein slow as crap it does not run everywhere anymore. Even if you automated the different screen sizes, performances, buttons, and so on...
      But at least you don't have to stick with the extremely minimal functionality of MIDP 1 or 2. ;)

      At least for me i can say that I will never write a program for a virtual machine ever again!
      If you *have* to compile a different version for every phone out there, you at least don't want it to be slow. ;)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    16. Re:Shouldn't matter with modern software. by ultranova · · Score: 1

      You missed precompiled binaries targeted for a certain architecture. None of the software I use on my computers runs off of a VM. It's either precompiled or bulit from the source. So yes, I would say it matters because I make it a point to avoid most things that use VMs.

      Both precompiled and self-built programs depend on a virtualization layer - kernel, drivers and libc - that conform to some specification - propably POSIX - to work. The last system where the programs talked directly to the hardware was MS-DOS, and even that provided a virtualization layer in the form of disk routines (and SVGA standard later). Virtual machines simply take this one step further by also virtualizing the CPU instruction set - but then again, just what is source code anyway, but a virtualization layer ?

      You can't avoid virtual machines with computers. You just can't.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    17. Re:Shouldn't matter with modern software. by WillerZ · · Score: 1

      Bollocks it is. I've tried it myself, since in some cases I have C code and Java code to solve the same problem. The startup time is still long, the periodic garbage-collection stall is still there, and the only way it's ever faster than native code is if some dumbass forgot to use the C compiler's optimiser.

      Java and/or gcj _can_ beat C code at low optimisation levels, but I've never seen it approach the performance you get out of xlc -O5.

      --
      I guess today is a passable day to die.
    18. Re:Shouldn't matter with modern software. by WillerZ · · Score: 1

      I don't see a Java-based processor anywhere.

      Here you go: http://www.opencores.org/projects.cgi/web/jop/over view

      --
      I guess today is a passable day to die.
    19. Re:Shouldn't matter with modern software. by Octorian · · Score: 1

      Then what you're telling me is that Ubuntu (and probably a lot of 64-bit Linux users/distributions) don't understand what Solaris has known for *years*...

      You can have a 64-bit OS, and run 32-bit applications!!!!

      And no, it isn't painful at all!

      In fact, on modern Solaris machines (where you pretty much always have a 64-bit kernel on UltraSPARC), most of the userland code is 32-bit. The only things that are 64-bit are drivers (kernel code), programs that actually have a need for 64-bit addressing, and the libraries needed to support them. (in other words, most core libraries are provided in both versions)

      Actually, IRIX does this too. Wouldn't be the least bit surprised of AIX did as well, but I've never had a 64-bit AIX machine.

      Probably the biggest reason people build apps 64-bit on their 64-bit PCs, though, is the extra optimizations for the x86-64 architecture that I've heard make a big difference. Sun even attacked this problem, by also supporting compilation targets that optimize for their newer 64-bit-capable processors while still building 32-bit code. (v8plus, v8plusa, v8plusb)

      I know this has to be possible in Linux, and the only problem is that many people havn't realized that it is easier than they think. Heck, I'm running SuSE 10 64-bit at home, and it actually installs 32-bit Firefox so all those wonderful plugins will still work.

    20. Re:Shouldn't matter with modern software. by j-cloth · · Score: 1

      You can't avoid virtual machines with computers. You just can't.
      I miss peeking and poking bits on my C=64 :(

    21. Re:Shouldn't matter with modern software. by AdolChristin · · Score: 0

      The ARM929 Chips even have a mechanism called Jazelle which allows Java byte code to be executed natively in hardware. This is another processor mode alongside the existing ARM and Thumb modes.

      --
      #include "forums.h"
      int main() {while (bollox) postcount++;}
    22. Re:Shouldn't matter with modern software. by aaronl · · Score: 1

      No, you can do what you're saying. It's just that if you do, you aren't really running 64 bit, since, as you point out, all your apps are 32 bit. Ubuntu-64 compiles everything targetted at AMD64, so you need to do crazy things to get it all to work and get most of the 32 bit platform installed along with your 64 bit stuff.

      The downside is having to have a 32bit C lib, 32 bit browser, 32 bit Java, etc. It quickly starts to eliminate the reason to try to run 64 bit if all of your software is targetted to IA-32.

    23. Re:Shouldn't matter with modern software. by Bert64 · · Score: 1

      There is a 64bit JVM already, the problem is things like flash which are only available as native binaries, and not for 64bit hardware.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    24. Re:Shouldn't matter with modern software. by CMonk · · Score: 2, Funny

      Any self respecting Java programmer knows better than to have a collection of class ModPoint. You need an interface for ModPoint that is implemented by AbstractModPoint from which ModPointImpl is derived. Let's not even get into ModPointFactory. What really kills me is the ModPointIterator...

    25. Re:Shouldn't matter with modern software. by Moofie · · Score: 1

      Fear not. Apple will be along soon enough to show everybody how it's done.

      --
      Why yes, I AM a rocket scientist!
  3. Intel is continuing development? by DurendalMac · · Score: 5, Funny

    Sheesh, the Itanic wasn't exactly a success story. How does it fit into their new roadmap with cooler chips that eat less power? That processor was a goddamn space heater.

    1. Re:Intel is continuing development? by Bing+Tsher+E · · Score: 1

      It wasn't ever targeted at the clone/screwdriver shop market. Which isn't to say that makes it good, or bad.

    2. Re:Intel is continuing development? by drgonzo59 · · Score: 2, Funny

      Well, some people are cold in the winter you know...

    3. Re:Intel is continuing development? by questionlp · · Score: 5, Interesting

      Although it may not run as cool and will use around 100W of peak power (+/- 10%), Montecito will be dual-core and run at around 1.6-1.8GHz at launch. 100W is less power than the current high-end Xeon MP and just over the Sun US-IV+ processors, but each of the two cores gets 12MB of L3 cache. Compare that to the ~120-130W power envelope of the mid/high-end Itanium processors available right now.

      Granted, the Itanium is not the fastest enterprise-focused processor out there, but at least they are trying to reduce the overall power consumption and heat generation of the next-gen Itaniums.

      For the workload I deal with everyday, the Opteron and US-T1 are better suited.

    4. Re:Intel is continuing development? by Anonymous Coward · · Score: 5, Informative

      Parent mocked:
      >Sheesh, the Itanic wasn't exactly a success story. How does it fit into their new roadmap with cooler chips that eat less power? That processor was a goddamn space heater.

      See: http://www.ideasinternational.com/benchmark/bench. html

      Make special note of the SPECint2000 page and SPECfp2000 pages and also make note of the TPC-C scores.

      The Itanium 2 takes the top three SPECint_rate_base2000 spots (128 cores), the top SPECfp_base2000 (single core) and the top two SPECfp_rate_base2000 spots (128 cores). The 64-way HP Superdome (by now they're all Itaniums, so they don't bother noting PA vs Intel) is in four of the top eight nonclustered TPC spots.

      In short, the Itanium 2 is the best scientific computing chip on the market, as proven by the SPEC_int_base2000 and SPECfp_rate_base2000 stats (beating out the Power5). Also, it's not too shabby on the TPC numbers, only being edged by the IBM Power 5.

      If you don't work with a 16+ core Itanium 2 or Power5, please STFU about them being market failures. They're not marketed at you.

    5. Re:Intel is continuing development? by Jozer99 · · Score: 2, Insightful

      Actually, if you think about it, the Itanium looks pretty good heat/performace wise compaired to the Pentium D's, which have roughtly the same heat output.

    6. Re:Intel is continuing development? by Billly+Gates · · Score: 5, Interesting

      Actually it was.

      THe Itanium has an impressive FPU set to make it fast in certain situations like scientific apps but other than that its been subpar and expensive compared to cheaper Xeon's and other risc processors like IBM's Power.

      The Mercedes was supposed to be the new Xeon for servers and workstations and NT with its portable HAL was supposed to eventually migrate to the chip and would overtake the desktop market after teh apps appeared. It was all teh rage at Zdnet computer magazines and was termed the next big thing by Intel.

      Mercedes (Itanium) was Intel's kneejerk reaction the Powerpc which was a threat in the early to mid 1990's.

      Mercedes was supposed to be here by 1997 and it still hasn't delivered its promise as the next platform out of x86. I get modded down every time I talk about the Itanium but the engineering specs and things that just went wrong are stunning. The first version never came out because it was too slow which delayed it for another 2 years for its next version. The next one(first publically released) had to be overclocked and require a 1 pound heatsink with a fan that sounded like a jet engine just to be nominal. Intel loaded it with huge cache to make it go faster in certain benchmarks which brought up the price and size of the chip. HP killed teh alpha next to make it look like the Itanium wasn't as slow in comparison.

      Carly Fiona did alot of strange things in terms of arm struggling Intel and forcing the cancellation of the Alpha in favor of the ITanium because she lacked the concept of "sunkin costs" or bad investments. Itanium does not make HP or Intel really any money. I am not talking about its technolical abilities but from a business standpoint.

      Switching to an alpha would have been better and cheaper with stronger performance. Windows2k was out in beta3 on it at the same time as x86 and Linux and BSD support was already strong. Not to mention HP already had VMS ported to it.

      The premise behind VLIW was that as chip says limits things you can do with hardware there needs to be a shift to software and leave the fast ram (cache) on the chip. Turns out huge improvements in fabrication made this argument false and somethings like branch predictions just can't be done in software. Fast dedicated hardware is faster than software. Who came up with this idea of moving optimization to software?

      If I were Intel I would can Itanium and start over. Transmeta had something interesting and the new PentiumM's are rumored to be designed by a small Isreali firm bought by Intel with similiar technology. I think that is the next big thing.

      Of course a newer Alpha would rock. Sigh

    7. Re:Intel is continuing development? by timeOday · · Score: 5, Interesting
      STFU about them being market failures. They're not marketed at you.
      That's Itanium's biggest failing of all. It was once intended to replace X86, now it has been pushed back into a tiny supercomputer niche where it will never pay off.
    8. Re:Intel is continuing development? by Jeff+DeMaagd · · Score: 1

      If nothing else, it is showing commitment to established roadmaps. That is important to high end and certain specialized needs, the only way they will commit to a new product is knowing whether it will be available a certain number of years. This is important so that a product doesn't have to go through a costly redesign for a different chip too often. If a manufacturer breaks that commitment, then it will be hard to regain that trust or even bother using that company's products in the next design.

    9. Re:Intel is continuing development? by Michalson · · Score: 1

      Mercedes (Itanium) was Intel's kneejerk reaction the Powerpc which was a threat in the early to mid 1990's.

      Mercedes was supposed to be here by 1997


      Back when I was in school I remember doing a little presentation on future methods of increasing computer power (like dual and quad setups [with the "new" Pentium Pro). The 64bit "Itanium" was in the presentation. As I said that was back when I was still in school. Still in high school.


      Transmeta had something interesting and the new PentiumM's are rumored to be designed by a small Isreali firm bought by Intel with similiar technology

      At least by name the team that designed the Pentium M (which is in Israel and was created by Intel about 30 years ago) is in house Intel, however I have no idea if the actual employees who did it where brought in from a bought out company. Judging solely by the chips coming out of Intels other facilities (slow, expensive, hot, very inefficent [both power and cycle wise]) it would seem to make sense that the Pentium M was designed by anyone besides the brain trust at Intel.

    10. Re:Intel is continuing development? by alexq · · Score: 1
      while i agree with some of your sentiment (being an ex-digital alpah group employee), i do have to question/point out some things:

      Mercedes was supposed to be here by 1997
      are you sure about that year? i know they had started designing it by then, but that seems a bit early for it to have actually ever been predicted to have come out, given the at least 4 year chip development cycle at intel.

      Carly Fiona
      you mean Carly Fiorina? :)

      The premise behind VLIW was that as chip says limits things you can do with hardware there needs to be a shift to software and leave the fast ram (cache) on the chip. Turns out huge improvements in fabrication made this argument false and somethings like branch predictions just can't be done in software. Fast dedicated hardware is faster than software. Who came up with this idea of moving optimization to software?
      I honestly don't understand the first sentence at all, and have no idea what you mean by "huge improvements in fabrication made this argumen t false"...?

      The main benefit the Intel designers saw in a VLIW-type architecture, as I understood it, were that they could explicitly easily state parallelizable instructions - thus giving more explicit instruction level parallelism to the processor. there was never any talk of doing branch prediction - or ANY optimizations - in software during runtime. All optimizations done in software for VLIW are done at compile time. In fact, that's the main argument against VLIW - is that we already do a lot of those optimizations anyway, and that modern compilers for superscalar processors output pseudo-VLIW code anyway, so perhaps there isn't much to be gained. Itanium obviously still does a lot of optimizations in the hardware, including branch prediction..

      Looking forward to elaboration on what I didn't understand in your post, though, to help clear things up. It helps to get the sentence structure right ;)

    11. Re:Intel is continuing development? by boner · · Score: 2, Informative

      While the Itanic is a nice piece of engineering, please consider the following. The EPIC (or VLIW) architecture employed in the Itanic really puts the burden of optimization at the compiler level. The current generation of compilers is really not good enough to fully leverage the Itanic's computing resources.

      While the SPEC and TPC-C numbers are impressive, please consider this: those numbers are the result of several compile-execute-profile iterations. These iterations provided the compilers with the information needed for their optimization decisions.

      SPEC reflects workloads that are in general repetitive in nature and are therefore correctly optimized using compile-execute-profile iterations. SPECfp accurately reflects the behavior of number crunching codes and various other flavors of scientific computing. However, the ad-hoc nature of OLTP and Datawharehousing workloads as seen in the real world cannot be as optimized as TPC-C. Workloads that have many data dependent execution paths cannot be efficiently optimized for the EPIC instruction set (other than through speculative branching). Therefore these ad-hoc workloads never reach the performance levels boasted by TPC-C results.

      The reason the Power5 edges out the Itanium on TPC-C is exactly for that reason. The RISC architecture allows easier optimization of data dependent execution paths.

      While the Itanic is indeed a decent scientific computing chip, price-performance wise it is not better than the AMD Opteron. The main reasons for Itanics high performance are the many parallel execution units combined with the large caches. Both are expensive, substantially decreasing the price-performance.

      According to some estimations (too lazy to find the link), it will take maybe two generations of compilers before the EPIC instruction set can really shine. Optimizing code at compilation time on the fly is hard and a lot of investment is needed into optimization routines to get that done properly. Great performance improvements are seen using compile-execute-profile, but currently (afaik) the best running code on Itanium is still hand tweaked. (Checkout: Itanium - A system implementor's tale, Charles Gray et.al. USENIX 2005)

      BTW, your last comment was uncalled for, Intel originally did market the Itanic as the be-all, end-all of computing. Although I would be interested to see pictures of a 16+ core Itanium 2+. My latest count of Itanium cores stopped at two. Did you mean 8+ dual core Itanium 2?

      just my 2 cents

    12. Re:Intel is continuing development? by Anonymous Coward · · Score: 0

      There's a lot of intel fanboys around who buy into whatever the latest excuses Intel pukes up for Itanium.

      That thing is the spruce goose of processors, that original anon cow can tell people to STFU all he wants, many of us here lived through the history of the claims by Intel of what Itanium was going to do.

      Anyone remember the year of Itanium? HAHAHA. Some year. That was 2 years ago I think.

      Oh well, it don't matter. Itanium is a sunk processor. It ain't going anywhere now or ever. Billions upon billions upon billions of $s of research money and Intel fanboys want us to believe they intended it to be a marginal niche player? Sure, sign me up for the swampland.

    13. Re:Intel is continuing development? by Anonymous Coward · · Score: 0

      Seriously, it is a waste we all know intel has compiler optimizations to the nth degree that IBM et all have not performed, and on artificial spec benchmarks peak power5 still wins. It is important to note in the real tests like databases, ibm is beating itanium in database performance with half of the processors. That is like saying sparc processors are super fast because the E25k with 144 processors is faster than and ibm with 32 cores. The truth is everyone in the high end space is doing more with less cost/power. Hell even the Opteron is competitive and it is using a brain dead arc from the 1970's and has a much smaller R&D/Manufacturing budget. The truth is the battle is being fought if AMD systems can scale, then the niche grows smaller. Already where I work intel blades have replaced sun and ibm systems and our big db servers are ibm power5 systems and mainframes.

    14. Re:Intel is continuing development? by supradave · · Score: 1

      Things that people don't realize is that it's not an x86 chip. A BIOS-like OS that takes advantage of what the Itanium can do will inherently be more secure than Linux or BSD or Windows.

    15. Re:Intel is continuing development? by sjames · · Score: 1

      now it has been pushed back into a tiny supercomputer niche where it will never pay off.

      It doesn't really fly in supercomputing either. Given the price/FLOP of Itanium nodes vs. Opteron or Xeon, the only way it sees any use there at all is primarily through hardware grants from Intel. Very few apps really do better on Itanium.

    16. Re:Intel is continuing development? by kittynicole · · Score: 1

      Average top price for an Itanium server on eBay is about $3,000 (according to the Mpire Researcher free eBay research tool). The far end of the bell curve is $6,000. Not too shabby, I wouldn't mind an extra three grand. Maybe now is the time to dump 'em on the market? ;)

    17. Re:Intel is continuing development? by ultranova · · Score: 1

      Things that people don't realize is that it's not an x86 chip. A BIOS-like OS that takes advantage of what the Itanium can do will inherently be more secure than Linux or BSD or Windows.

      "Inherently more secure" - in what way ? And why ? And BIOS-like in what way - it's loaded in ROM ?-)

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    18. Re:Intel is continuing development? by cnettel · · Score: 1

      But the fact that it even presents itself as a P6 and surely has several performance characteristics similar to P6 means that it is simply a development of P6. P6 was never exceedingly hot and had, compared to the architectures of today, high IPC. That Pentium Pro from high school is haunting you.

    19. Re:Intel is continuing development? by 15Bit · · Score: 1
      Having used Opteron, IBM Power, and Itanium 2's for scientific calculations i can 100% confirm this. If you can compile the software to properly take advantage of the architecture, the Itaniums are noticeably faster even than Power's on both single cpu and multi-cpu runs (i benched up to 128 cpus). The caveat is of course, that you can compile the code yourself, cos the Itanium performance is hugely compiler dependant.

      I would add that i also used Alpha's, and they were light years ahead of anything in their time but lag a long way behind the more modern Power/Itanium's for what i did. It would have been nice to see what would have come out if they hadn't been canned though.

    20. Re:Intel is continuing development? by Isca · · Score: 1

      certain aspects of Itanium research were incorporated inside the current architectures, so it's not all wasted money. The amount of money needed to upgrade the speeds and lower the power consumption is certainly worth the press on having the fastest supercomputers out there. At some point down the road, they may even be able to merge the cores back together - for 64 bit apps, it really does perform well. If 95% of programs out there are optimized for 64 bit, then software emulation of the other 5 won't really matter. Then he development that they have continued to do will really pay off.

      It's good that Intel has fallen on its face, unless you are an investor. This will only intensify the push to real innovation. I get the impression that intel is focusing on 2-3 years down the road with the processor changes they have implemented in the road maps. We might be talking about the "great chipmaker's" comeback at that point.

    21. Re:Intel is continuing development? by Sj0 · · Score: 2, Insightful

      "How much does that weigh?"

      "Ham!"

      Don't even TRY to critisize it.

      It's not FOR you.

      --
      It's been a long time.
    22. Re:Intel is continuing development? by Anonymous Coward · · Score: 0

      "I get modded down every time I talk about the Itanium but the engineering specs and things that just went wrong are stunning. The first version never came out because it was too slow which delayed it for another 2 years for its next version. The next one(first publically released) had to be overclocked and require a 1 pound heatsink with a fan that sounded like a jet engine just to be nominal. Intel loaded it with huge cache to make it go faster in certain benchmarks which brought up the price and size of the chip."

      The first version, Merced, severely underperfomed, but the improved follow-up cores (and compilers) haven't been that bad in the workloads the architecture has been designed for. Unfortunately for Intel, Opterons put up an unexpected fierce fight from below and (with Xeons) took away the high-volume portion of the marketplace. But Itanium's power consumption is justifiable for the oomph it offers -- again, in certain uses -- and of course a dedicated server/HPC chip has to have tons of cache. It's not like POWER5's 36MB of L3 per chip (144MB per 8-core module) means it's a flawed design :-)

      "Carly Fiona did alot of strange things in terms of arm struggling Intel and forcing the cancellation of the Alpha in favor of the ITanium because she lacked the concept of "sunkin costs" or bad investments. [...] Switching to an alpha would have been better and cheaper with stronger performance."

      Don't you mean PA-RISC there? (Which has been EOLed and will cease to produced in 2007.) The Alpha was somewhat marginal in HP's grand scheme of things, at best a leftover from Compaq (who in turn had serious plans for it when they got it with most of DEC).

      "Transmeta had something interesting and the new PentiumM's are rumored to be designed by a small Isreali firm bought by Intel with similiar technology."

      The Crusoes and Efficeons never fulfilled their promises. Their power-saving (which turned out to be the only good prospect about them) got quickly mitigated by similar technologies in Mobile Pentiums, and then the Pentium-M wiped the floor with any chip from Transmeta. (And as somebody pointed out, the brilliant team in Haifa, Israel is Intel's own. And unlike somebody else suggested, while the P-M is based on the P6 core [PPro/PII/PIII], there are so many new inventions in the branch prediction and resource utilization, and the power-saving tech -- such as turning temporarily un-accessed parts of the on-die L2 cache temporarily off -- that the Banias already deserved to be called a new chip design, let alone the new dual-core variants...)

    23. Re:Intel is continuing development? by sonpal · · Score: 1
      First you say:

      (1) Turns out huge improvements in fabrication made this argument false and somethings like branch predictions just can't be done in software. Fast dedicated hardware is faster than software. Who came up with this idea of moving optimization to software?

      and then you say:

      (2) Transmeta had something interesting

      I just want to point out that Transmeta did exactly what you are complaining about in #1... they moved optimizations to software, and proved that their solution was in the same performance ballpark while consuming substantially less power, because the underlying ISA was more power efficient.

      Now, if one can come up ISA is better performing - which is basically a function of chip area, because one can do more things in silicon instead of uOps if one has more transistors - and usually a much smaller area is dedicated to a hardware compatibility unit, then implementing the compatibility in software running on the primary ISA is going to result in better performance.

      At the processor level, hardware and software are pretty blurred. This is why CISC processors scream these days - the instructions are translated and optimized into a different ISA, which the processor actually executes well.

    24. Re:Intel is continuing development? by nelsonal · · Score: 1

      IIRC, the Pentium M isn't too far removed from the Pentium III line, which makes it sort of an extention of the Pentium Pro line from almost 10 years ago now. Odd how good ideas just keep getting reused and the newer ideas just fizzle after a few years.

      --
      Degaussing scares the bad magnetism out of the monitor and fills it with good karma.
    25. Re:Intel is continuing development? by zenslug · · Score: 1

      Judging solely by the chips coming out of Intels other facilities (slow, expensive, hot, very inefficent [both power and cycle wise]) it would seem to make sense that the Pentium M was designed by anyone besides the brain trust at Intel.

      This is offtopic, but I want to address the above comment that you made. I am no Intel fanboy, but I do work for a large, well-known company that also gets a lot of well-deserved gripes. But, as an engineer, it really irks me to hear people blame the engineers for poor products. From my experience, the vast majority of shitty products don't come from pure engineering decisions, but rather from confused business concerns. Bad products come from business people who don't understand technology, but they are the ones who hold the purse strings. These are the guys who seem to linger around in companies after the original players, the ones who create the great products, leave. The hype brings in the power-hungry know-nothings.

      This helps to explain why Google tends to put out decent stuff from a tech perspective. Right now the engineers have the ability to drive the projects that they want. Time will tell how long it will take until they need more business people, and those business people start making short term shitty decisions, too, at the expense of solid technology. It doesn't mean that the engineers who have been there from day 1 will become idiots, but rather it is the fact that their hands will be tied.

  4. Intel gets rid of it... by scenestar · · Score: 0, Redundant

    Amd implements it.

    I know what to invest in....

    --
    perpetually dwelling in the -1 pits
    1. Re:Intel gets rid of it... by Guy+Harris · · Score: 1
      Amd implements it.

      So did Intel, after AMD did.

  5. As noted elsewhere by C.+E.+Sum · · Score: 5, Interesting

    This is very old news. Various sources and die photos have showed this for more than a year... ...and no one cares.

    The die space reclaimed was somewhat significant, and the software emulation is faster than the hardware emulation.

    --
    -- Have you ever imagined a world with no hypothetical situations?
    1. Re:As noted elsewhere by muyuubyou · · Score: 1
      The news here's the poor choice of words this Gordon Haff has made. I'm guessing this analyst doesn't own any Intel stock.
      Basically, no one ever used hardware-based IA-32 execution, so better to use the silicon for something else. Of course, basically no one uses software-based emulation either, but at least that doesn't cost chip real estate.
      In other words, no one cares. Sounds like it's a worthless feature just so they can include it in the list. I'm not sure what's the market for this chip, having Xenons for so cheap.
    2. Re:As noted elsewhere by heavy+snowfall · · Score: 1

      Since you seem to follow this, do you know what they're going to use the die space for?

    3. Re:As noted elsewhere by raxx7 · · Score: 1

      It's not like Intel just popped out the IA32 circuit and droped some new stuff in that spot.
      Although it's microarchitecture is an evolution of the current Itanium2, the upcoming is a brand new chip, where Intel chose not to implemente the IA32 logic.

    4. Re:As noted elsewhere by C.+E.+Sum · · Score: 1

      Well.. how about all that jucy on-chip cache?

      --
      -- Have you ever imagined a world with no hypothetical situations?
    5. Re:As noted elsewhere by Anonymous Coward · · Score: 0

      The die space reclaimed was somewhat significant, and the software emulation is faster than the hardware emulation.

      LOL, SW emulation is faster than the hardware it runs on :-))))))) I mean, seriously wake up before you click the button :-)

    6. Re:As noted elsewhere by raxx7 · · Score: 1

      Or the couple of added execution units.
      Or the 1 MB L2 instruction cache.
      Or just saving sillicon area. :)
      They didn't remove it. They simply didn't implement it in the new chip.
      The IA32 compatibility required logic that not only took area, also sat in the critical paths. So, not implementing it simplified things a bit. Maybe a big bit.

  6. What he meant to say was.. by Anonymous Coward · · Score: 5, Funny

    "Of course, basically no one uses Itanium either..."

  7. why not Alpha by xx_chris · · Score: 5, Insightful

    if they are going to dump x86 compatibility, why not dump Itanium compatibility and just go back to Alpha?

  8. Extend the logic by bstadil · · Score: 3, Funny
    'Basically, no one ever used hardware-based IA-32 execution, so better to use the silicon for something else,' said Illuminata analyst Gordon Haff. 'Of course, basically no one uses software-based emulation either, but at least that doesn't cost chip real estate.'"

    Why not extend that logic? No one really used the Itanium chip anyway so why not use the silicon to make Yohan's for Apple?

    --
    Help fight continental drift.
    1. Re:Extend the logic by Bing+Tsher+E · · Score: 1

      Isn't there a whole family of server-class hardware from H-P that uses the Itanium? (as I said in a different comment tonight, not machines you'd buy at your local screwdriver shop) There's probably nary a motherboard at all made in Taiwan that has a socket for an Itanium.

    2. Re:Extend the logic by drinkypoo · · Score: 0, Troll

      How fucked up that you got modded troll. If anything, "Flamebait" would have been appropriate. However, I would choose Funny, or Insightful. Itanic crashed and sank, and they should just give up on it now if they can't get performance up dramatically somehow.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Extend the logic by Anonymous Coward · · Score: 0

      C'mon everyoen knows itanic is the unsinkable chip! it's got quadruple siced cache! surely it must run faster than processors running at nearly double the clockspeed(1.5 ghz vs 2.4-2.8ghz) with a redesigned for efficiency pipeline with dual cores(opteron 880)... that only has 2x1MB of cache!

      surely 8MB of cache with a 1.5 ghz core is what we need, not dual 2.4ghz cores. with a petty 1MB cache each.

      i mean, it's not like you pay an average of $3,000 less per opteron 880 vs an itanic... oh wait you do. doh! obviously it's worth more because it's got an intel logo ;)

    4. Re:Extend the logic by drinkypoo · · Score: 5, Interesting

      Yes, there is a whole family, and I think they sold like 2 units last year. I kid, I kid. However:

      For 2004: Intel misses Itanium sales mark by $26.6bn

      And this is biased, but more current: Reality Check: Itanium - A Sound Bet for the Future?

      From that article's sidebar:

      At a Glance: Is the Intel Itanium Processor a Sound Bet for the Future?

      • Consumes more power, generates more heat, costs twice as much as x64 processors
      • Dual-core version delayed until mid-2006
      • First dual-core version to ship with drastically reduced specifications
      • Major server vendors, including IBM and Dell, have abandoned development
      • Competitive pressure on the Intel Xeon Processor could force Intel to abandon the Itanium processor
      • Rapidly increasing x64 performance eliminating need for the Itanium processor

      The Intel Itanium Processor's Troubled Year

      • December 2004: HP hands off development and ownership of the Intel Itanium Processor to Intel
      • January 2005: Microsoft announces it will not support Windows XP on the Itanium chip
      • February 2005: IBM announces it will not support the Itanium platform in its latest chipset. "It is a function of the market acceptance of Itanium," said IBM CTO Tom Bradicich
      • September 2005: Dell announces it will not offer any Itanium processor-based servers
      • October 2005: Intel says the release of a dual-core Itanium processor has slipped to mid-2006, and that the common chipset with the Intel Xeon Processor, designed to reduce the Itanium processor's cost, has moved out to 2009

      Granted, Sun is pretty well biased, but itanic looks like it's long since sunk to me.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:Extend the logic by bstadil · · Score: 1
      How fucked up that you got modded troll

      I know. I thought it was pretty funny notably since the Itanium has done so poorly and the parent posting was so self righteous. In many ways I think /. is getting worse on the insights of its posted comments but the entertainment value of some of the comments is still unsurpassed.

      --
      Help fight continental drift.
    6. Re:Extend the logic by AaronLawrence · · Score: 1

      Yeah, they just have to drag it out long enough, gradually dissappear from view, so that the shareholders don't riot over the wasted money.

      --
      For every expert, there is an equal and opposite expert. - Arthur C. Clarke
  9. x86: Intel's biggest mistake by Spy+der+Mann · · Score: 1, Interesting

    Sheesh. It took them what, 15 years to realize that they needed to DUMP backward compatibility to become efficient? *cough* 640K barrier *cough*

    What strikes me is that only when they begin losing market share to AMD, they begin to search for design flaws (obviously they don't have time to waste in x86 emulation when they're falling behind)

    1. Re:x86: Intel's biggest mistake by wiredlogic · · Score: 2, Informative

      The 640KiB barrier was imposed by the IBM PC architecture not the 8086 hardware. The 8086 can directly address 1MiB of RAM. 4MiB if you isolate each of CS, DS, SS, and ES into their own banks with additional decoding logic.

      --
      I am becoming gerund, destroyer of verbs.
    2. Re:x86: Intel's biggest mistake by Guppy06 · · Score: 1

      Except AMD's 64-bit chips are backwards compatible. Thank God, too, because precious few desktop components have 64-bit drivers.

    3. Re:x86: Intel's biggest mistake by maynard · · Score: 3, Informative

      I don't seem to remember any "640K" barrier with the 8088 or 8086. Didn't it support up to 20 address lines? Yup... I thought so. That missing 384K was reserved for ROM, video RAM, and whatever else one might need. And lets not forget the bank switched expanded RAM boards that were around in the day. As one whose family owned an original XT w/ 20MB drive and full 640K from 1983 onward, I can say with assurance that 640K was a whopping amount of RAM in the day. It also cost a buttload.

    4. Re:x86: Intel's biggest mistake by El+Cabri · · Score: 1

      So I don't get the logic behind the politically-correct Intel bashing. On the one hand, one hears that Intel is bad because they have carried on with binary compatibility since the microprocessor pre-history (the 8086, even the 8080 to a certain extent), creating an architecture that is indeed in some places a bit quaint.

      Then on the other hand we are supposed to believe that AMD is genius for having led the way in moving to 64 bits through extension of that much-reviled x86 architecture rather than by starting from scratch with an innovative and modern architecture such as EPIC.

      So the bottom line is the Intel is always wrong, right ?

      Oh anyway, go and count how many www.top500.org supercomputers in the world are Intel powered, and how many are AMD powered. People who build supercomputing clusters must be clueless joe's who buy into Intel's evil marketing messages, right ? Because I see more "Itanics" than Opterons there, and way more Xeons than either of these.

    5. Re:x86: Intel's biggest mistake by Zencyde · · Score: 2, Insightful

      This is offtopic but... I'm glad to see someone using MiB rather than MB, that makes things so much simpler because of the way metric prefixes work. I salute you!

      --
      What day is it? Could you please tell me?
    6. Re:x86: Intel's biggest mistake by m50d · · Score: 1

      Oh yeah, look what a big success the itanium has been. And compare with the backwards-compatible amd64. Like it or not, dumping x86 backwards compatibility is not a good move.

      --
      I am trolling
    7. Re:x86: Intel's biggest mistake by drinkypoo · · Score: 1
      As one who had an IBM PC-1 with 64kB onboard and 384kB on an 8 bit ISA expansion board, all I can say is, I'm jealous :)

      I think the motherboard is still hanging on the wall at my friend's house. Hi, Scott!

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    8. Re:x86: Intel's biggest mistake by Tim+Browse · · Score: 1, Troll
      *cough* 640K barrier *cough*

      Damn, where's the (-1, Clueless) mod when you need it?

    9. Re:x86: Intel's biggest mistake by maynard · · Score: 1

      Yeah, well don't feel too bad. Dad was on the thing all the time I so I got the hand-me-down trash-80. Which -- honestly -- was a pretty cool computer as long as you didn't want to play Ultima III. :)

    10. Re:x86: Intel's biggest mistake by Detritus · · Score: 1

      You could also add a MMU to the processor. I knew someone who had an Altos 586 running multi-user Xenix. It used an 8086 and a custom MMU.

      --
      Mea navis aericumbens anguillis abundat
    11. Re:x86: Intel's biggest mistake by Vellmont · · Score: 1

      Wrong on both counts. Intel initially planned Itanium to be a replacement for x86. To help in that transition they created a translation layer that they believed would be necessary until vendors made IA64 compiled binaries. The only "inefficiency" is the extra silicon needed to accomplish this, and the IA64 architecture isn't gimped because of it.

      I highly doubt losing market share to AMD has anything to do with the decision to dump x86 compatibility on a chip level. No one is using the x86 compatibility, and it also being available in software has made hardware emulation rather pointless. If I remember correctly Intel has for a long time said that the hardware compatibility would go away at some point.

      I do agree they should have done it years ago, as soon as the software emulation was available. It only adds more die space and more expense. Apple is now in their 3rd CPU transition, and has never had chip-level backward compatibility. Instruction translation is really only necessary for anything where performance isn't a huge concencern, but the newly compiled version isn't available yet, or never will be. (Like say UPS monitoring software). Anything where high performance is a concern should be re-compiled anyway, or why would you even consider switching to the new chip?

      --
      AccountKiller
    12. Re:x86: Intel's biggest mistake by tap · · Score: 1

      Why not take a look at the top500 list? They have a nice piechart by processor family. We can see that there are more AMD X86-64 systems than IA-64 systems. You also have to keep in mind that there is a large lag time from when a top500 system is planned and when it's actually purchased, installed, and makes it on the list. Opteron is a newer processor and adoption takes times. Expect to see a huge increase in the number of opteron systems on the next list.

    13. Re:x86: Intel's biggest mistake by pnewhook · · Score: 0, Offtopic

      Come on, these alternate prefixes are just stupid. Using MB is not confusing at all.

      --
      Tesla was a genius. Edison however was a overrated hack who liked to torture puppies.
    14. Re:x86: Intel's biggest mistake by Billly+Gates · · Score: 1

      Newer doesnt make it better.

    15. Re:x86: Intel's biggest mistake by raftpeople · · Score: 3, Insightful

      Intel's biggest failure was taking so dang long to get the Itanium to market. I remember when it was annouced, and a short decade later the thing arrived. By the time it arrived things had changed quite a bit at HP, Intel and the computer markets in general.

    16. Re:x86: Intel's biggest mistake by pnot · · Score: 1

      I don't get the logic behind the politically-correct Intel bashing.

      I don't get the logic behind describing Intel-bashing as "politically correct".

    17. Re:x86: Intel's biggest mistake by Billly+Gates · · Score: 2, Insightful

      business users typically run ancient software from companies or consulting comapanies that no longer exist in binary form only. COmpatibility is more important for Intel than a company like Apple.

      People who buy pc's do so because its what everyone else buys.

      Its a mess and I am glad I am not Intel. I bet HP has a contract forcing Intel to keep making the Itanium too. They killed the alpha for Itanium and its just astounding after what a few billion in sunkin costs can do to make sure you wont leave for something better.

      I think Alpha had a much better chance of taking over. W2k beta3 was out at the same time of the x86 version and Linux and BSD already were ported. HP could keep VMS and their other oses without porting them to another platform. The alpha had great FX32 software and I think some basic hardare assisted x86 emulation but I could be wrong? I remember reading back in 97 that the emulation was as fast as a pentium 166 on the 250mhz alpha. Pretty impressive.

      Some mass production to lower costs and more software resulting from Intel and HP being behind it could have brought the windows based software to the platform as well. Just like Apple by now I bet we all would be using alpha based systems. Intel would of had a strong edge over AMD as well as teh AlthonXP would be struggling to compete.

    18. Re:x86: Intel's biggest mistake by Zencyde · · Score: 4, Insightful

      Yes it is, because MB means 1000 Kilobytes, and MiB means 1024 Kibibytes. Usually you're off by a factor of about 0.91 or 1.1, which can mean a lot. Please don't insult the functionality of accuracy. :D

      --
      What day is it? Could you please tell me?
    19. Re:x86: Intel's biggest mistake by pnewhook · · Score: 1

      Who cares? I have a 240 GB harddrive . Does it really matter if I meant 1000x1000 or 1024x1024 ? How anal can you get?

      --
      Tesla was a genius. Edison however was a overrated hack who liked to torture puppies.
    20. Re:x86: Intel's biggest mistake by Anonymous Coward · · Score: 0

      Pop quiz: Name a reason you might need to refer to 1,000,000 bytes.

    21. Re:x86: Intel's biggest mistake by Zencyde · · Score: 3, Informative

      250 or 240? I'll just use the 240 number. 257,698,037,760 bytes using the GiB system. 240,000,000,000 bytes using the GB system. over 17 gigs difference, and you're telling me you won't notice it? :P

      --
      What day is it? Could you please tell me?
    22. Re:x86: Intel's biggest mistake by Zencyde · · Score: 3, Funny

      Memory allocation while coding. :P

      --
      What day is it? Could you please tell me?
    23. Re:x86: Intel's biggest mistake by afidel · · Score: 1

      Much more important than killing Alpha is the fact that they killed PA-RISC development for Itanium. Alpha was a niche processor with a declining market population, high powered workstations and specialized scientific servers. PA-RISC ran/runs big business systems which have very specific requirements that are outside what a comodity processor will be targeted at due to cost concerns, but where the system price guarentees room for profit. Being without a big bad processor for their high end business systems would be MUCH worse for HP then having to use an alternative processor for their limited workstation and scientific server lines (Opteron, Xenon).

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    24. Re:x86: Intel's biggest mistake by pnewhook · · Score: 1

      Nope. Wouldn't notice and wouldn't care if I did.

      Besides, when you refer to computers, K and M always refer to 1024 and 1024x1024. Simply because 1000 is not that practical to represent. Some slimy marketing people may use 1000 though to over inflate the published capacity.

      --
      Tesla was a genius. Edison however was a overrated hack who liked to torture puppies.
    25. Re:x86: Intel's biggest mistake by Zencyde · · Score: 3, Insightful

      They do, hard-drive companies use the metric standard when listing sizes, while Windows will read it in the ibi-prefix standard. Which is why you lose about 10% of your data capacity upon purchasing a hard-drive. :P

      --
      What day is it? Could you please tell me?
    26. Re:x86: Intel's biggest mistake by 2short · · Score: 1

      Yes, hard drive marketers slimily redefine MB to make their capacities seem bigger. They are not doing it because it is a standard.

    27. Re:x86: Intel's biggest mistake by KC1P · · Score: 1
      Intel has tried several times to dump backward compatibility in the past, and they've been burned each time, so they're right to be a little hesitant.

      The 80286 didn't have a sensible way to get back to real mode, because Intel assumed that once the 286 came out everyone would immediately switch to pure protected mode software to enjoy that luxurious 16 MB address space. Didn't happen -- at the time 1 MB was a lot (I could only afford 128 KB on my IBM PC), and after two years DOS was already entrenched. So the 386 backpedaled and added V8086 mode (further improved in the Pentium with VME).

      Then the Pentium Pro got lazy about loading segment descriptors, which Intel figured was OK because everyone should have switched to 32-bit flat code by then so they wouldn't notice (since the segment registers would be loaded once and never again). Wrong again, the PPro was terrible at running 8088 or 80286 code (i.e. Win 3.1), so they went back to doing it right in the Pentium II.

      Meanwhile, AMD has been diligent about making sure that new features don't come at a big cost to backwards compatibility, and it's worked out really well for them. When Intel gets ahead in the benchmarks, it's often just because their latest gimmick instruction set add-on (SSE7 or whatever we're up to now) plays directly to whatever the fad is that year, but their performance on basic integer instructions (y'know, the stuff that OSes are written in) stands still or even jumps backwards (early P4s).

      So even when Intel has been ahead in the magazine benchmarks, AMD's CPUs have usually still been faster for doing real work (i.e. not video games or decompressing porn), and Intel knows it. The Itanic 1's absolutely awful x86 performance is probably what killed its market share more than any other single thing. Unusably slow is no better than totally incompatible, and if that were OK (and the market were really a fair fight on the technical merits of competing architectures) then the Alpha would have taken over the world years before and none of this would have ever happened.

      Anyway, how many bits do we really need? I'm getting really sick of doubling the number of address/data bits every ten years, and breaking everything for a while each time, especially when it's obviously an ego thing as much as anything else. Let's decide how many bits we need now, then someone (CGB?) could design a nice clean instruction set, and we could just skip a few steps and start using 2048-bit CPUs now.

      It'd take decades to max out on that ... and I'd love to write code that I know will still run long after I'm dead, without all the new kids whining about "why are we still lugging around this stupid 512-bit compatibility mode, anyone who still writes programs that would fit in less than 4 quincentdecabytes is a wuss anyway!"

    28. Re:x86: Intel's biggest mistake by nogginthenog · · Score: 1

      It was still a shit design!

    29. Re:x86: Intel's biggest mistake by WillerZ · · Score: 1

      The novel "Sense and Sensibility" is a little more than that.

      --
      I guess today is a passable day to die.
    30. Re:x86: Intel's biggest mistake by ultranova · · Score: 1

      Sheesh. It took them what, 15 years to realize that they needed to DUMP backward compatibility to become efficient? *cough* 640K barrier *cough*

      Speaking of 640k barrier, DOS still works on todays x86 processors, due to them being backwards compatible by booting to a 16-bit real mode. So no, you don't need to dump backwards compatibility to be efficient.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    31. Re:x86: Intel's biggest mistake by ultranova · · Score: 1

      Pop quiz: Name a reason you might need to refer to 1,000,000 bytes.

      Memory allocation while coding. :P

      Why not simply use the sizeof macro ?

      Better yet, don't bother with allocation, just change the pointer to a random value, ignore SIGSEGV and see what happens ;). I think several of the programs I use employ this method ;(.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    32. Re:x86: Intel's biggest mistake by ChunderDownunder · · Score: 1
      their latest gimmick instruction set add-on (SSE7 or whatever we're up to now)

      SSE3, I believe. SSE4 is no doubt on the horizon, primarily because Apple users will note that Photoshop doesn't seem as zippy as when it was optimised for altivec. :)

    33. Re:x86: Intel's biggest mistake by Frumious+Wombat · · Score: 1

      That's true, which is why when a local company donated a pile of parts from a failed project to my college, I took the IBM 360 Emulator board. I lost 2 XT slots, but it backfilled my ram to 640K. Too bad the software we had never worked right, as it would have been college-age nerd cool to be the only OS/360 user in a VMS shop. A PC-XT, Hercules (real) MGA adapter, 40M HD, running Wordstar. It may still be the least obtrusive computer I ever owned.

      --
      the more accurate the calculations became, the more the concepts tended to vanish into thin air. R. S. Mulliken
    34. Re:x86: Intel's biggest mistake by Ilgaz · · Score: 1

      I understand what you mean. I (and some rare powerpc defenders) were being blamed for zealotry when we panic about Mactel announcement and this was one of the first things I am afraid from Intel switch, the needless (Really!) compatibility stuff back to 8086 even.

      If they keep this attitude, Mactel won't be that bad. I mean Mactel as a replace for G5 workstations, not "imac" or "Powerbook" line.

      As using "Mactel switch defender" people's words, Apple completely made it software based to emulate 68k chips when PowerPC switch has been announced. Nobody died or something and I believe you can still use 68k stuff on PPC macs (not Intel).

      _IF_ they keep this attitude in prosumer line of CPUs, half of my reasons calling Intel move a step to backwards will be gone.

      Well, PPC is still a great cpu family and Apple used worst models ;)

    35. Re:x86: Intel's biggest mistake by don.pratt · · Score: 1
      Yes it is, because MB means 1000 Kilobytes, and MiB means 1024 Kibibytes.

      If you're in the marketing department, then yes. Otherwise, the computer industry has historically used KB to refer to 1024B and MB to refer to 1024KB.

      Please don't insult the functionality of accuracy

      I'm not. I'm insulting the idiocy of hard drive marketers who decided to inflate their numbers rather than stick with accepted industry terminology.

    36. Re:x86: Intel's biggest mistake by ArbitraryConstant · · Score: 1

      "Yes it is, because MB means 1000 Kilobytes, and MiB means 1024 Kibibytes. Usually you're off by a factor of about 0.91 or 1.1, which can mean a lot. Please don't insult the functionality of accuracy. :D"

      MB means 1048576 bytes either way, unless it's coming from a storage vendor.

      --
      I rarely criticize things I don't care about.
    37. Re:x86: Intel's biggest mistake by Billly+Gates · · Score: 1

      Slashdot used to run on an alpha server back in the day. Alpha's were not that niche and I remember big businesses on wall street (I lived in New York) loved alpha based NT 4 domain controllers. They are the only thing that could handle tens of thousands of user accounts without slowing down.

      Alpha's were used for some servers and alot of workstations. They really began to become popular somewhat but digital was dieing at the same time. Also Microsoft products were tuned for x86. SQL Server was a disappointment on the alpha as many large businesses standardizing on Microsoft wanted unix/VMS based scalability and hoping SQL server on an alpha would be scalable enough.

      But the alpha died when Carly Fiona wanted to kill it and promised not to update anymore. It has not been updated since 1999 even though the 8th generation alpha was already in beta testing. What a shame and they were economical.

      PA-Risc were expensive and specialized and more like IBM's power chip for large systems. Correct me if I am wrong since I never used them before? I heard great things with Pa-riscs in domes and HP decided to put Itaniums and Xeons instead in teh domes and converted them to windows. Very not good for mission critical things like nuclear powerplants. Windows and Xeon's are not in the same league.

      Alpha was teh fastest chip for sure and not that much more expensive than a standard pentium. They made great linux boxes and used standard pci busses for peripherals.

  10. Might as well, makes sense! by Anonymous Coward · · Score: 0

    Might as well dump x86 from the core. They are right, who would buy an Itanium to run x86 code? Of course, who would buy an Itanium for just about any thing? Very few people want to code for EPIC, I think the industry has pretty much prooven that point by following AMD's lead with x86-64. But for those who do use Itanium it makes more sense to pump up that on die cache!!

  11. What is Itanium good for, anyway? by realmolo · · Score: 1, Interesting

    Seriously. Is there any reason to buy one of the things? What does it do that justifies ANYONE buying one? Does it still have the "best" floating-point performance?

    1. Re:What is Itanium good for, anyway? by Anonymous Coward · · Score: 0

      They are often associated with large cache's, which is awesome for some applications. But those are off chip, so maybe that is just a coincidence.

    2. Re:What is Itanium good for, anyway? by drinkypoo · · Score: 1

      It still has the best fp performance for a single chip, and it still isn't worth it on a price-performance ratio when you consider multiple-core athlons, or even multiple-core late-model pentiums.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:What is Itanium good for, anyway? by friedmud · · Score: 4, Interesting

      I work in Computational Engineering and can say that I know people who specifically write for epic because it is good at pushing the _huge_ amounts of serial computations (mostly solving large systems of equations) through the processor quickly.

      I have personally had a dual itanium workstation sit under my desk for around 9 months. It was ok I suppose. I was doing Finite Element mechanical simulations on it and it did fairly well at it (it helped that it had 8 Gigs of RAM). I also got Gentoo compiled on it (this was before it was really supported) and it worked fairly well as a desktop (had an nvidia quadro card in it).

      Personally, I think intel should just give up... they obviously lost the fight. But who knows, maybe it is actually making them _some_ money (although it can't be much).

      Friedmud

    4. Re:What is Itanium good for, anyway? by m50d · · Score: 4, Insightful

      If you have the time to hand-optimize your code, it blows anything out of the water. This means it's useful for simple number crunching, but not much else - more processors are generally cheaper than more coders. It was expected that compilers would improve by the time Itanium was adopted, but that hasn't really happened. (I read here that the hurd coders were able to make their Itanium message-passing routine TEN TIMES faster by doing it in hand-coded assembly compared to what a compiler churned out)

      --
      I am trolling
    5. Re:What is Itanium good for, anyway? by aachrisg · · Score: 1

      Is it faster than a cluster of as many commodity dual core amd64s you can buy for the same amount of money? Faster than GPGPU code on as many 7800GTXs as you can buy for the same amount of money?

    6. Re:What is Itanium good for, anyway? by Anonymous Coward · · Score: 2, Informative

      These are my personal opinions and not those of my employer.

      Some users are:
      - Certain well-tuned scientific and engineering applications that are floating-point intensive but not memory bandwidth bound. Ideally, the code should have few branches. There is a significant performance bonus for code that can fit fithin the L3. However, the per/processor cost delta over the Opteron is difficult to justify for the standard 2 processor per node compute cluster model.
      - Large systems. SGI can support up to 512 processors and 6 TB of memory in a seamless single system image today. This is useful if you need to run applications that require large contiguous memory maps, e.g. certain computational chemistry applications (this is why there is a single half-terabyte system sitting in the room next to me). Additionally, 1-2 microsecond MPI latency is a major benefit for huge MP applications (Pathscale's new Infinipath adapters are very close, however) .
      - Real world supercomputing. The difficulty of porting and developing code to Blue Gene cannot be understated- A high linpack score is not necessarily reflective of real-world performance.
      - I/O bandwidth- (this is particularly more SGI specific than IA64), the IA64-based Altix is particularly good at streaming large amounts of data. For example, a single 3700 IO-brick has 6 independent 133MHz PCI-X busses (12 ports total). A single system's IO subsystem can handle over 3 gigabytes per second sustained read and write.

    7. Re:What is Itanium good for, anyway? by Anonymous Coward · · Score: 0

      I use 7800 GTs (not GTXs) for a lot of things, but they have very annoying instruction limits and only 32-bit floats. This makes them quite limited for my needs, and although I use them everywhere I can (simply 'cause they are the fastest things I have), I still have to use opterons for a lot of stuff. Just one itanium box would be as good as 2 or 3 opteron boxes. The only reason I don't have one is that for the price, opterons are much more useful in other types of workloads.

      Itanium is a great architecture for scientific or 3D graphics work - its just too damn expensive for people like me to consider seriously.

    8. Re:What is Itanium good for, anyway? by LurkerXXX · · Score: 1

      I think that would depend on what it was used for. If you are running software on it that is licensed per CPU as many commercial packages are, the up front cost of the Itanium CPU might be vastly vastly outweighed by the cost of the licenses for the additional AMD64s chips.

    9. Re:What is Itanium good for, anyway? by Anonymous Coward · · Score: 0
      Is it faster than a cluster of as many commodity dual core amd64s you can buy for the same amount of money?
      That depends on what you plan to run. If you plan to run something that scales well, probably not -- the price difference is probably greater than the performance difference. If you need the best straight-ahead serial computation speed, or if money is no object, then you're one of the few people who are better off with an Itanic.
    10. Re:What is Itanium good for, anyway? by Compuser · · Score: 1

      Would you say they should close the business and return the money to the shareholders?

    11. Re:What is Itanium good for, anyway? by m50d · · Score: 1

      In terms of direct hardware cost, no, but once you factor in power, cooling, networking, physical space, admin etc., yes. If they weren't, they wouldn't sell.

      --
      I am trolling
    12. Re:What is Itanium good for, anyway? by Anonymous Coward · · Score: 0

      "But who knows, maybe it is actually making them _some_ money (although it can't be much)."

      There's no way it can be making Intel a cent. They've spent billions on it so far, and so has HP -- and HP has said they're committing to spend *another* 3 billion to continue marketing it. Which they have to, since Itanium has turned out to be PA-RISC's replacement and nothing more, other than the occasional HPC win.

      Meanwhile, sales are flat at about 8,000 systems a quarter, 80 percent of those being HP systems. You can map any increase in Itanium sales to an even larger decrease in PA-RISC sales. In any given quarter, IBM POWER systems outsell all Itanium systems by four to one, and Sun SPARC systems outsell all Itanium systems by eight to one. It's a fairly safe bet that HP is getting their processors at a very favorable price from Intel, so where does Intel stand any chance of making enough profit to even start to recoup their investment?

      What may be true is that at least for now it would cost Intel even more money to drop Itanium than it would to keep going, due to contractual obligations.

    13. Re:What is Itanium good for, anyway? by VAXcat · · Score: 1

      Only reason to buy one is that it's the current hardware implementation that runs VMS...

      --
      There is no God, and Dirac is his prophet.
    14. Re:What is Itanium good for, anyway? by friedmud · · Score: 1

      It could also be that while they aren't _making_ money they aren't losing _too much_ and it would be more devastating to lose the capabilities by shutting down that production line and laying off all those people.

      I've seen this in business before where you need to keep some expertise around until you figure out where to go next and while you're figuring it out you lose a little bit of money but in return you maintain your agility in that business sector...

      Friedmud

  12. In that case..... by KeiichiMorisato · · Score: 2, Funny
    'Basically, no one ever used hardware-based IA-32 execution, so better to use the silicon for something else'

    Why not just say....

    Basically, no one ever used Itanium , so better to use the silicon in a more meaningful manner...

    1. Stop making Itanium chips
    2. Harvest saved silicon
    3. ????
    4. Profit!

    Given ???? involves *cough* implants of some type....
    Imagine Intel branded implants.

    I'm talk about cyborg implants, what were you guys thinking about!!

    1. Re:In that case..... by ettlz · · Score: 1
      Given ???? involves *cough* implants of some type....
      Imagine Intel branded implants.

      So where would the "Intel Inside" stickers be placed?

    2. Re:In that case..... by Anonymous Coward · · Score: 0

      Ah, I see you went to the South Park Underware Gnomes School Of Business too!

      1. Collect underware
      2. ???
      3. Profit!

      Imagine... Intel branded underwear... implants... heh

    3. Re:In that case..... by Anonymous Coward · · Score: 0
      I'm talk about cyborg implants, what were you guys thinking about!!

      The intense pain coursing through the language centre of my brain as it attempts to parse meaning from your message.
    4. Re:In that case..... by ultramk · · Score: 1

      You know, silicon and silicone are not the same thing. Common mistake.

      Silicone jubblies are pretty common in LA, for example.

      Silicon jubblies are best enjoyed in HD (DOA4 for e.g.).

      m-

      --
      You catch enchiladas by picking them up behind the head and holding them underwater until they don't kick anymore -VeGas
    5. Re:In that case..... by KeiichiMorisato · · Score: 1
      The intense pain coursing through the language centre of my brain as it attempts to parse meaning from your message.

      Curses! Posting on Slashdot while working = grammatical and spelling errors.

      I apologize for the pain I have caused.

    6. Re:In that case..... by KeiichiMorisato · · Score: 1

      Yes silicone is different from silicon, but silicon is the starting point for making silicone! Therefore harvesting silicon -> ??? -> profit! Still works!

    7. Re:In that case..... by Anonymous Coward · · Score: 0

      Defintely not on the forehead!

  13. Irony .... somewhere by WasterDave · · Score: 4, Funny

    There's a sense of irony with Apple having, apparently, no problem getting PPC emulation to work on an Intel x86 ... and Intel having no joy running x86 emulation on IA64. If I didn't know better it would look to me like IA64 is a bag of crap.

    Oh, hang on.

    Dave

    --
    I write a blog now, you should be afraid.
    1. Re:Irony .... somewhere by bazald · · Score: 1

      Irony? I don't see what is unexpected about this. The PPC chips used in Apple computers weren't all that powerful relative to their new x86 chips. On the other hand, x86 computers are at least comparable in power to the IA64 architecture chips. Emulation of worse chips is easier than emulation of better ones... at least when it comes to real time performance.

      --
      Insert self-referential sig here.
    2. Re:Irony .... somewhere by PaulBu · · Score: 1

      Yeah, especially since (thouse of us old enough should remember ;-) ) one of the original goals of PPC consortium (IBM, HP, Motorola) was to optimize its architecture so that it is able to efficiently emulate "other processors" (meaning especially x86). RISC purists were disgusted by PPC because it had all those extra instructions... I guess ISA simplicity goes both ways and not it makes it easy to emulate PPC on x86...

      BTW, what's happening with TransMeta these days?

      Paul B.

    3. Re:Irony .... somewhere by ArbitraryConstant · · Score: 1

      "Well not really. Apple isn't really emulating PPC on the x86...since they WROTE the operating system that is running on both they have a lot more control over what's running and can do all kinds of cool translations and on the fly stuff for what the program is doing, making it not really emulation. More like how WINE is not really an emulator."

      That is not correct.

      Rosetta runs binaries of a different architechture. The fact that does this with translation makes it fast, but it doesn't make it not an emulator.

      WINE makes it possible to run binaries that conform to different standards but use the same architechture. Some people call what WINE does emulation too (acronym notwithstanding). I don't know if I'd go that far, but Rosetta is certainly an emulator.

      --
      I rarely criticize things I don't care about.
    4. Re:Irony .... somewhere by Edmund+Blackadder · · Score: 1

      No there is no irony here. Just an persistent eagerness to mention apple in every slashdot story no matter how unrelated.

      People should start moderating these offtopic.

    5. Re:Irony .... somewhere by WasterDave · · Score: 1

      Just an persistent eagerness

      Is it related to a urge to be a grammar nazi?

      Dave

      --
      I write a blog now, you should be afraid.
    6. Re:Irony .... somewhere by moosesocks · · Score: 1

      Believe me. PPC emulation on an x86 was no easy feat for apple, and has been considered the holy grail of CPU emulation for the past 10 or so years.

      I'm vague on the details (someone fill me in here...), but there are a few intrinsically difficult obstacles to emulating a powerpc on an x86 at a realistic speed. Until PearPC (about a year ago), nobody could properly execute a ppc binary on an x86 machine unless they wanted to run it around 1/100 of its intended speed.

      From what I recall, apple purchased the technology behind rosetta from a small firm. It's really quite an accomplishment, and I only hope that Intel keeps its act together. I can't say that I fully approve of intel's engineering decisions over the past 5 or so years (the Pentium M being the sole exception). I wouldn't be surprised at all if AMD takes the hint and radically increases production capacity to lure apple into using their chips. I also wouldn't be surprised at all if the first-generation x86 xServes used AMD server chips. They're really that much superior to anything intel's got.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    7. Re:Irony .... somewhere by ricky-road-flats · · Score: 1
      Is it related to a urge to be a grammar nazi?
      *cough* I think you mean "an urge"...

      :-)

    8. Re:Irony .... somewhere by cnettel · · Score: 1

      Yes, but you don't have to emulate the whole system, just user mode down to libraries. For GUI refresh (especially a compositing GUI), you can get that done in native code, if done right.

    9. Re:Irony .... somewhere by ChunderDownunder · · Score: 1
      On wine architecture emulation, Darwine does in fact aim to emulate a different CPU via qemu.

      rosetta - PPC --> x86.

      darwine - x86 --> PPC.

      But now Macs are x86 too... :)

    10. Re:Irony .... somewhere by ArbitraryConstant · · Score: 1

      "Yes, but you don't have to emulate the whole system, just user mode down to libraries. For GUI refresh (especially a compositing GUI), you can get that done in native code, if done right."

      True. And that makes it efficient. But it doesn't make it not an emulator because the translation to local libraries happens in addition, not in lieu.

      --
      I rarely criticize things I don't care about.
    11. Re:Irony .... somewhere by Foerstner · · Score: 1

      Irony? I don't see what is unexpected about this. The PPC chips used in Apple computers weren't all that powerful relative to their new x86 chips. On the other hand, x86 computers are at least comparable in power to the IA64 architecture chips. Emulation of worse chips is easier than emulation of better ones... at least when it comes to real time performance.

      You've been listening to too much Apple "2-3x faster" marketing hype.

      For instance, there are now quite a few benchmarks of the Core Duo iMac. There's the Ars one that was shown on Slashdot a while ago, and the Macintouch one.

      The Core Duo iMac, with two x86 cores, is a very small improvement over the single PPC970. Compared to a two-and-a-half-year-old dual-CPU Power Mac G5, the Core Duo iMac is pathetic. And this is running Intel-native applications like QuickTime and iTunes.

      --
      The US free market: two halves of a government-granted duopoly are free to set the market price.
    12. Re:Irony .... somewhere by ArbitraryConstant · · Score: 1

      "The Core Duo iMac, with two x86 cores, is a very small improvement over the single PPC970. Compared to a two-and-a-half-year-old dual-CPU Power Mac G5, the Core Duo iMac is pathetic. And this is running Intel-native applications like QuickTime and iTunes."

      The thread on the Ars article goes into detail about why the benchmarks weren't done very well, and you're ignoring Macintouch's own caveats with their numbers. It's clear Apple still has a lot of optimization to do before they reach the level of refinement they had on PowerPC, and plenty of the stuff where people are complaining it's not twice as fast is I/O bound.

      I've noticed three things with the benchmarks: First, single-threaded benchmarks still show an advantage for the Intel machine. It's small, but it's still there meaning the cores are fast individually. Next, I/O bound benchmarks still show an improvement, even though the hard drive is essentially the same. This is probably a result of Intel's chipset having a faster SATA controller, and having the chipset provided is another clear advantage of the switch.

      Finally, all the reviews have made a point of saying how responsive the machine feels. As these things are desktop machines, that's probably more important than any of the other performance measures. It's faster in other ways, but responsiveness is what you'll notice day to day.

      --
      I rarely criticize things I don't care about.
    13. Re:Irony .... somewhere by ArbitraryConstant · · Score: 1

      "Yeah, especially since (thouse of us old enough should remember ;-) ) one of the original goals of PPC consortium (IBM, HP, Motorola)"

      Wasn't it Apple, IBM, and Moto? The acronym everyone uses is AIM.

      "I guess ISA simplicity goes both ways and not it makes it easy to emulate PPC on x86..."

      Not really. It's actually pretty difficult to emulate PowerPC on x86, and Rosetta isn't that fast. It's impressive because it doesn't completely suck, but I wouldn't call it fast.

      --
      I rarely criticize things I don't care about.
  14. Let's see, Intel down 5.7%; AMD up 12% oh-x86? by postbigbang · · Score: 0, Troll

    Why waste real estate on that old, non-proprietary, open, well known and licensed x86 stuff when we can pull everyone down the rosy path towards the real goal of this HP-Intel PA-RISC-64-bit wonder? SO WE DON'T HAVE TO WORRY ABOUT THE BEGGARS STEALING OUR IDEAS ANYMORE.

    Mr Grove? Mr Grove? Your pacemaker's not working. We think it's the chip..... we couldn't find a way to port the code. Hello Mr Ruiz? Can you give Mr Grove a hand here? We think he's dying.

    --
    ---- Teach Peace. It's Cheaper Than War.
    1. Re:Let's see, Intel down 5.7%; AMD up 12% oh-x86? by Anonymous Coward · · Score: 0

      No emulation No p4 No p-m No x86 from intel
      if they did that when they first released the itanium
      AMD would be nowhere.

  15. Re:why not Alpha by Anonymous Coward · · Score: 5, Insightful

    Politics. Yes, Alpha is a much superior platform, technically speaking, than pretty much anything else out there today. But for Intel to turn their back on Itanic (thank you, Register, for consistently misnaming the Itanium in such an apt way) would mean admitting that the billions of R&D they spent on it was a waste. HP also has political reasons to not resurrect Alpha.

    Damn shame, that. If they'd poured as much money into Alpha as they did into Itanic, they'd have a platform that would whomp all over everything currently in the marketplace.

  16. HP-UX userland? by Anonymous Coward · · Score: 0

    If I run "file" on apps in the HP-UX 11.23 userland (e.g. /bin/sh), it reports they are "IA-32" executables. That would suggest "somebody" is using IA-32 emulation, unless I'm misunderstanding the output I'm seeing...

    1. Re:HP-UX userland? by Chuck_McDevitt · · Score: 1

      Yes, you are misunderstanding. IA-32 is Itanium native, but 32-bit, code. Not x86 code.

    2. Re:HP-UX userland? by msbsod · · Score: 1

      HP is doing the same 32-bit nonsense with VMS. Instead of adapting everything for pure 64-bit code, they still waste their and our time with 32-bit vs. 64-bit compatibility. We have the same problem of backward compatibility on the Alpha (for many The 64-bit processor). Dealing with a mixed address space is a software developer's nightmare.

    3. Re:HP-UX userland? by ctr2sprt · · Score: 1
      IA32 is Intel's name for x86. It never really caught on because I don't think they started using it until the Pentium, when "x86" obviously stopped making sense. It may well be that HP is confusing things by misusing the term, but I assure you, IA32 is x86. Look at Intel's 32-bit ISA documentation on their site if you don't believe me. Since the P3 at least they've exclusively used IA32 to describe the "x86" ISA.

      The "I" is for Intel, not Itanium.

    4. Re:HP-UX userland? by SillyNickName4me · · Score: 1

      Dealing with a mixed address space is a software developer's nightmare.

      A small comfort maybe, its no better with IRIX, while 64bit MIPS cpus have been around for 'some time' now as well, the last version I used (6.5.something) still had 32 and 64bit libraries, and a whole bunch of 32bit binaries (but then, it did also run on the older r4000 and the like still)

    5. Re:HP-UX userland? by daverabbitz · · Score: 1

      >A small comfort maybe, its no better with IRIX, while 64bit MIPS cpus have been around for 'some time' now as well, the last version >I used (6.5.something) still had 32 and 64bit libraries, and a whole bunch of 32bit binaries (but then, it did also run on the older >r4000 and the like still)

      The way I was explained it (with regards as to why my ultrasparc uses 32bit userland), is that 32/64bit refers to address pointers and that 64 bit address pointers introduce a performance penalty (not sure why).

      My understanding is that 32 bit binaries compiled for a 64bit arch still have the benefits of 64 bit math (and mov's?), but use 32 bit address pointers, so as to use less memory or whatever it is that makes them better. I could be wrong about that, but if it's optimised for a ultrasparc v9, why not use the v9 64 bit reg's, since it's not going to run on a 32 bit sparc anyway.

      Can anyone with a clue explain that better? Please no trolls raving about how 64bit is uber fast and will pwn my noobage box please.

      On a related note amd64's are faster because they have a better instruction set and more registers, not because of 64 bit math(which all machines since the P-Pro have anyway, mmx anyone?).

      Or so I'm told, I've never had a chance to do any tests or profiling on an amd64, and gcc -m64 doesn't work on my Sunblade 100 under Gnu/Gentoo/gcc3.3 .

      --
      What could be better than a jet powered motorcycle? http://www.youtube.com/watch?v=u8l6GTHLSWE
    6. Re:HP-UX userland? by BigCheese · · Score: 1

      The guy in the office across from me had the unplesant task of moving the bulk of the memory of one of our VMS apps to the P2 address space. Needless to say it involved a lot of swearing. 64 bit support in OpenVMS is not all that great.

      --
      The obscure we see eventually. The completely obvious, it seems, takes longer. - Edward R. Murrow
    7. Re:HP-UX userland? by Anonymous Coward · · Score: 0

      If I run "file" on apps in the HP-UX 11.23 userland (e.g. /bin/sh), it reports they are "IA-32" executables. That would suggest "somebody" is using IA-32 emulation, unless I'm misunderstanding the output I'm seeing...

      Only if somebody is using this hypothetical HP-UX 11 on Itanium!

      If a source tree is compiled on an Itanium, does it make a sound?

    8. Re:HP-UX userland? by Guy+Harris · · Score: 1
      and that 64 bit address pointers introduce a performance penalty (not sure why).

      You've guessed at least part of it:

      but use 32 bit address pointers, so as to use less memory

      Data structures with 32-bit pointers are smaller than those with 64-bit pointers, so the data structure takes less of a chunk out of your cache (hopefully reducing the number of cache misses, where you have to fetch stuff from slower main memory) and less of a chunk out of your main memory (hopefully reducing the number of page faults, where you have to fetch stuff from an even slower disk or file server).

    9. Re:HP-UX userland? by daverabbitz · · Score: 1

      >Data structures with 32-bit pointers are smaller than those with 64-bit pointers, so the data structure takes less of a chunk out of >your cache (hopefully reducing the number of cache misses, where you have to fetch stuff from slower main memory) and less of a chunk >out of your main memory (hopefully reducing the number of page faults, where you have to fetch stuff from an even slower disk or file >server).

      so was I right that if you define a Uint64 (not sure what the non-sdl name for that is) on a sparc v9 or sgi64 or mmx, it uses 64 bit math in a 32bit object file, and does it use 64 bit reg's mem-cpy's (wait is memcpy a kernel or libc function) on those platforms.

      Just curious, that's all.

      --
      What could be better than a jet powered motorcycle? http://www.youtube.com/watch?v=u8l6GTHLSWE
    10. Re:HP-UX userland? by Guy+Harris · · Score: 1
      so was I right that if you define a Uint64 (not sure what the non-sdl name for that is) on a sparc v9 or sgi64 or mmx, it uses 64 bit math in a 32bit object file, and does it use 64 bit reg's mem-cpy's (wait is memcpy a kernel or libc function) on those platforms.

      I don't know - I don't have any of those machines handy.

      If you compile something as "pure" 32-bit code, it presumably doesn't use 64-bit registers, as "pure" 32-bit code is supposed to run on 32-bit processors that don't have 64-bit registers.

      Some 64-bit systems might support what one might call "mixed" 32-bit/64-bit code, which allows all 64 bits of registers to be used but has 32-bit pointers. In "systems" I include the OSes and the compilers - the OS (kernel and/or user libraries) would have to support 32-bit pointer types but still allow all 64 bits of registers to be used.

  17. no, actually by HishamMuhammad · · Score: 0, Troll

    That means x86 is a bag of crap. I bet you can emulate PPC nicely on IA64 too.

  18. A sign of pressure? by marshallh · · Score: 3, Insightful

    Perhaps this is an indication that Intel has finally realized that their strangehold on the CPU market may be threatened by AMD? And that they will have to optimize and trim the fat off their products? Competition is good.

  19. Corrected headline by Anonymous Coward · · Score: 2, Funny

    There's obviously a typo in this headline, which I've corrected:

    Iintel Dumps Iitanium's x86 Hardware Compatibility.

    C'mon Slashdot editors, get with it.

    1. Re:Corrected headline by identity0 · · Score: 1

      Dunno if that was a joke or a mistake, the typo is in the extra 'I' in 'Itanium' - psst, it's not 'Iitanium', guys.

    2. Re:Corrected headline by TeknoHog · · Score: 1

      iI'm sure the extra 'i' is there simply to emphasize iIntel's cooperation with Apple ;)

      --
      Escher was the first MC and Giger invented the HR department.
    3. Re:Corrected headline by ChunderDownunder · · Score: 1

      Xserves will be using Iitaniums now???

  20. not invented here? by ScottCooperDotNet · · Score: 2, Informative

    Could it be the old "not invented here" syndrome?

    1. Re:not invented here? by Kelson · · Score: 1

      Considering they eventually caved and started implementing AMD's x86_64 architecture (though they're not willing to call it that), I don't think it's the case. Clearly they realized that the market for 64-bit chips with 32-bit x86 compatibility was all in EM64T/AMD64, so Itanium could focus on 64-bit only stuff.

    2. Re:not invented here? by networkBoy · · Score: 1

      What?!?
      The CEO has stated that Intel was planning 64 bit addressing and such long before AMD announced it, but had not anticipated the market being ready as soon as it was. Intel was not playing catch up from a design standpoint so much as from a marketing standpoint. Realistically the market window was closer than Intel thought, a mis-step yes, caving in? not at all.
      -nB

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
  21. The 486 on core is VERY, VERY slow... worthless by theendlessnow · · Score: 2, Informative

    This is a good thing. The Itanium can emulate the x86 faster than the 'good for nothing' 486 that was on core. It's worthless and NOBODY has been using it for a LONG time.

  22. About time by msbsod · · Score: 2, Interesting

    I think removal of the x86-emulation from the Itanium CPU was overdue. It should have never made it into the chip. Every serious software developer would have re-compiled their code on the new chip anyway. What I wish to see next is a dramatic reduction of the power consumption and return to the original promise by Intel to make the Itanium a replacement of the aging x86 architecture, not only for expensive servers, but also for desktop and notebook PCs. The x86 is smashhit because it is available for so many different applications. The Itanium however was pushed into a niche.

  23. No one uses Software Emulation? by logicnazi · · Score: 1

    What about the PPC emulation on the new intel macs?

    --

    If you liked this thought maybe you would find my blog nice too:

    1. Re:No one uses Software Emulation? by Keruo · · Score: 1

      Anyone have those new macs and want to dig in deeper to the emulation?
      Did apple do cherryos and just ported pearpc to run on macos? (unlikely, but hey, wild speculation is still allowed)

      --
      There are no atheists when recovering from tape backup.
    2. Re:No one uses Software Emulation? by Anonymous Coward · · Score: 0

      www.google.com

      Rosetta Transitive

      Yay!

    3. Re:No one uses Software Emulation? by Guy+Harris · · Score: 1

      Where did it say "no one uses software emulation" in the article? They were saying nobody was using the hardware emulation of x86 in the Itaniums, so they were going to remove it from the next Itanium 2 and use just, err, umm, software emulation.

  24. Might as well... by Trailer+Trash · · Score: 0, Redundant

    clear off the rest of the chip, since nobody uses itanium, anyway...

    1. Re:Might as well... by Anonymous Coward · · Score: 0
      Excellent Idea. So I guess the pinout of the new "chip" would look something like this?
      +----+
      | .. |-0 Vcc +5v
      | .. |-1 Gnd
      +----+
      They're going to make a killing selling thsese things at $400 a pop.
    2. Re:Might as well... by Anonymous Coward · · Score: 0

      Intel could add a couple more pins to your chip and call it a Ming Mecca..

  25. as soon as... by Sebastopol · · Score: 3, Funny

    ...Intel figures out what to do with the probably thousands of people working Itanic, they'll drop it. You can't just nix such a huge project and bone all the employees. I suspect they've been wanting to drag this thing out back and shoot it for some time, I mean it gets ZERO real estate or marketing attention on the website or corporate SEC prospectus info. Never read about it adding to bottom line in any filings.

    Maybe they just make it for the supercomputer folks... a niche market which is probably 10x larger and 100x more profitable than the propeller-beanie AMD fanboy crowd that trolls around here, scoffing at neon-illumiation-free chassis.

    --
    https://www.accountkiller.com/removal-requested
    1. Re:as soon as... by PornMaster · · Score: 1

      I wonder if they're just trying to keep it alive and not lose too much money while they fulfill some kind of contractual obligations to HP. I'm sure they'd have to pony up some cash to HP if they just dropped it.

    2. Re:as soon as... by msbsod · · Score: 2, Informative

      OpenVMS/Itanium - two excellent products, very closely connected, and both pushed together into the niche market in absolute silence. The same happened to OpenVMS/Alpha. What a waste!

    3. Re:as soon as... by timeOday · · Score: 1
      the supercomputer folks... a niche market which is probably 10x larger and 100x more profitable than the propeller-beanie AMD fanboy crowd that trolls around here, scoffing at neon-illumiation-free chassis.
      Oh, that must be why Cray, SGI, and Itanium are so ridiculously profitable.
    4. Re:as soon as... by bhima · · Score: 1

      I'm not disagreeing with your main point but a quick googling reveals that Itanium sales are measured in the billions of dollars. So SOMEONE must be using them!

      --
      Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
    5. Re:as soon as... by Sebastopol · · Score: 1

      Oh, that must be why Cray, SGI, and Itanium are so ridiculously profitable.

      This comment (a) makes no sense, even with the bad sarcasm, and (b) doesn't comprehend my statement.

      I'm comparing the tiny hard-core gamer market to the global supercomputer market. My observation is: there are more supercomputer CPUs out there than hard-core gamer CPUs. Now consider that 1 Itanic yields ~5-10x the profit of one P4EE ($2000 vs $200), and that supercomputer folks buy them buy the thousands. Heck, the US gov't has more supercomputers than Cray and SGI put together (does SGI even MAKE a supercomputer?).

      Why am I even explaining this to you??? Oh, I'm bored...

      --
      https://www.accountkiller.com/removal-requested
  26. Irony .... Where? by vanka · · Score: 2, Informative

    I'm not sure what your point is with that comment, Apple's emulation of the PPC architecture (Rosetta) is all done in software, which doesn't run at native speed. As I recall, the Itanium had software emulation of x86 at first, then they added I guess they added hardware emulation. Now to cut costs and chip real estate they are taking out hardware emulation and reverting to software emulation. I'm missing the irony in this particular situation. How is this ironic?

  27. Re:why not Alpha by cold+fjord · · Score: 1

    Alpha was great.

    Alpha was intended to have a 25 year life. Unfortunately, it is drawing close to the end of 25 years. The design team is gone. By the time they could reconstitute it, train everyone, start a design, get it through fab, and ready for production systems, it would be close enough to 25 years that it wouldn't matter anyway. There is also the ugly N.I.H. factor which makes it unlikely they would ever revive it. I'm afraid Alpha is gone. R.I.P.

    --
    much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
  28. Just waiting for... by Anonymous Coward · · Score: 0

    ...the confirmation from Netcraft. Is Intel dying?

  29. Itanium future has potential by Jherek+Carnelian · · Score: 1

    Here's a surprisingly cogent article (surpisingly so for a hobbiest web site like anandtech, that is) about how trends in cpu manufacturing processes may make Itanium a bigger winner in the near future:

    http://anandtech.com/printarticle.aspx?i=2598

    1. Re:Itanium future has potential by Helios1182 · · Score: 1

      I would say that anandtech is a step above a simple "hobbiest" site. They have put out a lot of very good in depth articles on various technologies. Memory architectures, pipelining, various GPU things, and many more that I can't think of off the top of my head.

    2. Re:Itanium future has potential by AcidPenguin9873 · · Score: 2, Insightful
      Here's a large problem with Itanium: It is an in-order architecture.

      This means anytime it misses in L1, the entire machine stalls waiting for the data to come back from L2/L3/memory. This is fine for applications where the compiler can figure out all the data dependences and schedule the code to hide these cache misses (i.e. scientific applications). It is not good for your run-of-the-mill GUI programs like Word, Firefox, your favorite email reader, etc. Out-of-order architectures like Pentium Pro/II/III/4 and Athlon hide L1 misses a LOT better because other (independent) instructions can execute while the cache miss is going on.

      A few points brought up in the article that I'll respond to:

      • Predication - Predication (conversion of if/else code with branches to branchless straight-line code using predicated instructions) is not limited to EPIC/Itanium architectures. Conditional movs (cmov) in x86/AMD64/EM64T are a watered-down version, but they suffice for a lot of simple situations such as the one the article brings up.

      • Instruction Level Parallelism (ILP) - Sure, the Itanium can decode/execute/retire up to 6 instructions per clock. That's dependent on two things: a) the compiler finding 6 independent instructions to schedule every clock, b) no L1 cache misses occurring (remember, Itanium is in-order, cache miss = stall).

      • ILP is dead anyway - CPU cores are much faster than memory. Any time you have to go to main memory for something, you take a HUGE hit in performance. Who cares if your CPU core executes 100,000 instructions in 0.00001 ns if it takes 100,000 cycles to bring a cache line in from memory? Memory bottlenecks are starting to dominate CPU performance (see this paper for more info), so single-thread performance is going to be dominated by how well the cores mitigate cache misses. Out-of-order cores can do this well (it's getting harder, read the paper), but it's difficult for in-order cores.

      • Thread Level Parallelism (TLP) - Any benefits of TLP stated in the article will apply to dual-core out-of-order processors in the same way they will apply to Itanium processors.

      • Power - Intel just came out with their dual-core mobile stuff. AMD will sometime before the summer. The article claims that performance per watt is superior for Itanium; that may have been true a year ago, but it's about to not be true.

      • Floating point performance - Itanium is the fastest FP chip on the planet. However, a lot of consumer apps aren't floating point-intensive, they're non-FP apps like Word, Firefox, an email client. Performance of these apps, like I said before, is much more dependent on not having cache misses dominate performance. Plus, with SSE2/SSE3 taking over all the FP duties in the latest Athlon64/Xeon/P4s, and Intel and AMD concentrating their efforts on improving those functional units, I bet consumer-level FP performance goes up.

      Now, one predicted trend for the future is for all architectures to move to simple, cheap, in-order cores, and put a lot of them on the chip to give increases in TLP without using a hugely complicated, expensive, lots-of-power-and-chip-area out-of-order core. From what I can tell, Itanium is a hugely complicated, expensive, in-order core, not exactly what we need to put 16 cores on a chip. Intel could easily resurrect the original Pentium core, retrofit SSE/SSE2/SSE3 to it, maybe add some runahead execution stuff (from that paper I linked to above) or maybe two-pass pipelining to mitigate the cache misses, and voila: a cheap, in-order core.

      Oh yeah, this is all academic anyway; backwards-compatibility (x86 has it, Itanium doesn't) is probably going to be the real driving force like it has been for the past 6 years.

    3. Re:Itanium future has potential by ArbitraryConstant · · Score: 1

      Nice post. I have one thing to add:

      "Now, one predicted trend for the future is for all architectures to move to simple, cheap, in-order cores, and put a lot of them on the chip to give increases in TLP without using a hugely complicated, expensive, lots-of-power-and-chip-area out-of-order core."

      While TLP will undoubtedly become more important in the future, I think the single-thread performance is going to remain important in the future, at least for the desktop. It's already hard to get significant amounts of parallelism out of most applications (even though most have several threads, most threads sleep most of the time), and the developer effort required to optimize for multiple cores increases dramatically with each one you add. Ultimately, I think this means we'll be stuck with chip designs that maximize ILP, to the detriment of the core count.

      There are applications for which TLP is not a problem, for example the servers that will run Niagara chips. But they have more sources of work (many clients making requests). I don't think desktops will ever have it that easy.

      --
      I rarely criticize things I don't care about.
  30. Who Cares? by raider_red · · Score: 2, Funny

    I'm sure that both of the users of the Itanium are thrilled by this development. They should drop it and use the extra fab capacity to make 8-bit microcontrollers. There's still a market for those.

    --
    It's good to use your head, but not as a battering ram.
  31. And the thing is by Anonymous Coward · · Score: 0

    Because other people did commit to Itanium, they all need to keep spporting it at least for a reasonable amount of time (including some upgrades and spare parts).
    This is good Bussines practice...

    But then again, it's not a semi technical supposedly "Insightfull", anti Intel argument so most people here would not understand...

  32. Where have all the good designers gone? by kerecsen · · Score: 5, Interesting

    I find is odd that Intel keeps backtracking to its 20 year old Pentium Pro design. Both of their recent high-budget designs, the P4 and the Itanium proved to be a flop to some extent, while the P6/Pentium Pro/PII/PIII/Centrino/Banias architecture has scaled amazingly well since its humble 200 MHz beginnings.

    Was there a generation change at the design offices? What else could have caused the most prominent chip design firm to lose its ability to do solid engineering? Granted even the golden boys created a dead end (i960) architecture, it wasn't quite as expensive a mistake as Itanium...

    I remember that in the nineties new chip generations would be popping up left and right, each of them offering some really unique and cool innovation in terms of memory management, execution streamlining or heat management. But Transmeta was the last memorable innovation, and since then everyone seems to be exclusively focused on cache megabytes and transistor sizes. I would love to see real experimentation and innovation reintroduced in the CPU arena...

    1. Re:Where have all the good designers gone? by diegocgteleline.es · · Score: 1

      Laptops running powerful dual-core CPUs eating less than 30W means nothing to you? Dualcore desktops alone are the biggest change in the CPU world since people started having computers in their homes, IMHO.

    2. Re:Where have all the good designers gone? by Edmund+Blackadder · · Score: 3, Interesting

      I do not think it has much to do with design. It has much more to do with inertia.

      Back in the day when new architectures were popping up like mushrooms, there just was not as much software out there. Therefore, it would be easier for somebody to come up with a workable system based on a new architecture. But more and more software is being created and the users are getting higher expectations in terms of the software they expect to have running on their systems. It is getting harder and harder to provide the ammount of software sufficient to make users happy.

      It seems that free software is a good solution to this problem -- all you have to do is compile a bunch of free software to our new architecture and viola -- you have an operational system. If I were Intel I would compile and provide official Itanic support for every major OS piece of software. This way the major problem Itanic has -- lack of software would be solved.

    3. Re:Where have all the good designers gone? by the_humeister · · Score: 1

      Now that's not quite fair. You might as well say that the K8 architecture is nothing more than a K7 with HT and on-die memory controller.

    4. Re:Where have all the good designers gone? by mihalis · · Score: 1

      I find is odd that Intel keeps backtracking to its 20 year old Pentium Pro design.

      Come on, 20 year old? I make it just over 10 since the processor was released...

    5. Re:Where have all the good designers gone? by Anonymous Coward · · Score: 0

      Sun UltraSPARC-T1 processor.... 8 core, 4 thread per core. CMT is innovation.

    6. Re:Where have all the good designers gone? by be-fan · · Score: 1

      That's true, but that's not really a chip design triumph so much as it is a process engineering and circuit layout triumph.

      --
      A deep unwavering belief is a sure sign you're missing something...
    7. Re:Where have all the good designers gone? by tomstdenis · · Score: 1

      And you'll be surprised to learn the newer cores are more of the same.

      Where things will be improving are DDR2/DDR3, more cores [e.g. 4 core], more efficient process and other things along those lines.

      The actual AMD64 core [excluding the x86 ISA] is actually fairly efficient. It's not the best but it's better than Intel's netburst and [so far] Pentium M line.

      Would be cool to see a move away from x86 even if it meant simple O(n) pre-decoding [e.g. no decoding optimizations]. That would make the die simpler but raise the memory bandwidth.

      Aside from that AMD could improve the L1 cache. It's currently a 2-way 64KB code/data cache. With say this they may be able to bump that up to say 128KB 4-way code/data. The trick there though is to keep latency to a minimum. 4-way may be too much.

      But even 128KB of 2-way would be nicer.

      Or even say 2MB L2s :-)

      Tom

      --
      Someday, I'll have a real sig.
    8. Re:Where have all the good designers gone? by ArbitraryConstant · · Score: 2, Insightful

      "I find is odd that Intel keeps backtracking to its 20 year old Pentium Pro design. Both of their recent high-budget designs, the P4 and the Itanium proved to be a flop to some extent, while the P6/Pentium Pro/PII/PIII/Centrino/Banias architecture has scaled amazingly well since its humble 200 MHz beginnings."

      We hit the wall in single-threaded performance that was remarkably similar for all the various architechtures. I imagine the Pentium Pro architechture appeared at a time when it was possible to incorporate most of the features we've come to know and love in something approaching their current form.

      "But Transmeta was the last memorable innovation, and since then everyone seems to be exclusively focused on cache megabytes and transistor sizes."

      I'd say Cell and Niagara are pretty interesting. They don't have the general-purpose utility of other chips, but they're very good at what they're specialized for, and they're certainly interesting.

      --
      I rarely criticize things I don't care about.
    9. Re:Where have all the good designers gone? by BigCheese · · Score: 1

      Actually it was HP and Intel. Much of the problem with the Itanium is while the EPIC architecture sounds like a really good idea in practice it has never worked all that well. Much of the philosophy behind EPIC is to move all optimization from the CPU to the compiler. Well, HP, Intel and lots of people with giant brains have tried to make the first great EPIC compiler but so far, no luck.

      --
      The obscure we see eventually. The completely obvious, it seems, takes longer. - Edward R. Murrow
    10. Re:Where have all the good designers gone? by afidel · · Score: 3, Interesting

      The i960 was not a failure, it's used in about 50% of RAID controllers and quite a few other embedded applications. Perhaps you were thinking of the i860, or the i432? The i860 was in many ways similar to Itanium. It was a VLIW (Very Long Instruction Word) architecture which was like EPIC very overreaching for the time. It was also a floating point monster that was expensive to produce. Finally the i860 required massive compiler optimizations to produce efficient code which the compilers of the day weren't up to. Basically Intel didn't learn from the i860 and repeated the mistake a decade and a half later.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    11. Re:Where have all the good designers gone? by mikelang · · Score: 1

      The reason: industry benefits from status quo. The new engineer doesn't necessarily have a way to put his new chip, because there is awesome amount of money needed to develop it. The situation could change once there would be enterprise decoupling between physical details of the manufacturing process and the designer group. It has already begin, but still the processors need to be migrated through many steps of complicated technologies, that need to be licensed for an awesome amount of money...

    12. Re:Where have all the good designers gone? by Phil+John · · Score: 1

      10 since it was released. Now, lets add 6months - 1year for ramping up production and we're at 11. But wait! What good is ramping up production if you have no chip design to produce from? Lets add another few years for that. Ok, now I'm not saying that 20 years is factually correct, but 15-16 years is definitely (in my mind) feasable.

      --
      I am NaN
    13. Re:Where have all the good designers gone? by Ilgaz · · Score: 1

      It will be kind of worse since Apple switched to x86 too.

      Remember G3 and G4 and even G5 can/could be alternative to x86. Imagine if Apple stayed on PPC and IBM and/or Motorola ships another Altivec like invention ahead of its time and makes all x86 looks backwards.

      Now it is just x86 out there. Of course you can buy a PowerPC workstation (a real one, like IBM one) but no more home competititon.

    14. Re:Where have all the good designers gone? by Anonymous Coward · · Score: 0

      But the Banias really is a chip design triumph. Compared to the PPro/PII/PIII core it has far better branch prediction abilities, and far more innovative power saving measures (such as powering down execution units and even unaccessed parts of L2 cache, and then back up immediately on demand) than any mobile versions of the former. While fabbing advances (and bigger caches, and nowadays dual cores) have played a part, mere manufacturing it's not the whole reason why it's such a good and promising line of chips. (Perhaps raw FPU performance notwithstanding, but hopefully SSE4 addresses that "when it's done".)

  33. Re:First Post by tylerni7 · · Score: 0, Troll

    Face it Intel... you just can't make processors as good as AMD does. Why don't you just go back to making that other stuff you make so we- oh... right.

  34. Re:why not Alpha by diegocgteleline.es · · Score: 1

    They'd have a platform that would whomp all over everything currently in the marketplace

    Well, Alpha was a high-end CPU designed for servers. Somehow, I doubt it could whomp the portable market? (which is a important part of the computer world these days)

  35. Indeed by Anonymous Coward · · Score: 2, Interesting

    I think the days of it mattering what the exact instruction set is are pretty much over.

    Indeed-- which is why it's hilarious that pretty much the entire world is just this moment moving to a single common unified instruction set. The server world has standardized on x86-64, Itanium is a walking corpse; the PC world has standardized on x86 as well, PPC has retreated to video game systems. We are moving to a new world of processor agnosticism, at the exact same time processor agnosticism has become largely pointless.

    1. Re:Indeed by captaineo · · Score: 2, Insightful

      Plus the fact that modern processors do so much internal magic on the code stream that an "instruction set" is more of a transmission protocol than anything having to do with CPU internals.

  36. Athlon64 should to it too. by mnmn · · Score: 1

    The same real estate is also taken up on the cheap Athlon64 we all use. In time, when theres enough x64-based software out there AMD should release 64-bit-only chips (meaning remote the legacy parts... of course there are still 32-bit instruction in a 64-bit chip (think ARM)). Since theres so much software out there already, all you need is a new bootloader. The extra space could hold more cache, initial 8mb part of the RAM space running at 1x speeds or quite possibly the southbridge chip itself to cut costs much further.

    But until Windows x64 is stable, I'll continue to use the 32-bit parts of my Athlon64.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    1. Re:Athlon64 should to it too. by tomstdenis · · Score: 2, Informative

      You really ought to read up on the AMD64 design. There is little advantage to ignoring 32-bit opcodes. First off, "64-bit opcodes" are actually extensions of 32-bit ones. That is, 32-bit code can [and often is] smaller than 64-bit code [except when there are a lot of register spills].

      Second, the hardware real estate is not that much. If the cpu only did 64-bit opcodes [hint: think something as simple as adding two char's] you'd have MORE overhead as you mask off bytes, words, dwords.

      Aside from cache and the ALU decoder space is where there is waste.

      Better designs would be to keep the ALU and drop the ISA [or at least re-arrange the opcode map to favour more common opcodes ... ala huffman!].

      Tom

      --
      Someday, I'll have a real sig.
    2. Re:Athlon64 should to it too. by Anonymous Coward · · Score: 0

      Only problem with that is the 8086/DOS compatability. (The crap that the init known state of the CPU is in 8086 real mode and the firt instruction it executes is at ffff:fff0 or something liek that) The BIOS and Windows HAL/Loaders would need to be rewritten. That is not technicaly hard of course, but I'd say there is much political/marketing resistence to that.

      As a historical foot note, I believe SGI released a X86 box with no DOS compatability. :)

  37. Re:why not Alpha by SillyNickName4me · · Score: 1

    they'd have a platform that would whomp all over everything currently in the marketplace.

    And that is exactly why it isn't happening, everything currently in the marketplace is for a substantial part comming from... Intel.

  38. Just one thing by Andy+Dodd · · Score: 2, Informative

    The Itanium was known as Merced (for a river in Oregon or Washington, I believe), not Mercedes

    --
    retrorocket.o not found, launch anyway?
  39. Re:why not Alpha by Anonymous Coward · · Score: 0

    Yes, I often take my Itanium servers to the WIFI enabled city park. The fresh air makes them more HA. 4U servers are very portable these days, only about 60lbs light.

  40. Re:why not Alpha by maraist · · Score: 4, Interesting

    Damn shame, that. If they'd poured as much money into Alpha as they did into Itanic, they'd have a platform that would whomp all over everything currently in the marketplace.

    I don't know that I agree. The alpha was a particular set of optimizations. Dual register files, branch-prediction hints. pure 32bit (sub-32 bit data access had to be emulated through a multi-step process). Deep pipeline (for it's day).

    But at the same time, they purposefully witheld adding out-of-order execution (plays havoc w/ their highly optimized register configuration). Sparc had similar problems with their rolling register-stack.

    I studied the alpha prior to the announcement that their new version would have out-of-order, so I don't know if they ever did go that route.

    The point is that by adding all of the techniques that were employed by modern CPUs (aside from slightly higher speed memory), they would not have maintained much of an advantage. Their performance would be comparable to the AMD-64, but not much faster.

    I'd still love to see the alpha kept alive, there was absolutely nothing wrong with it, except it's price (for general work-station use).

    --
    -Michael
  41. Of course... by IGnatius+T+Foobar · · Score: 1
    Of course, basically no one uses software-based emulation either, but at least that doesn't cost chip real estate.
    Of course, basically no one uses the Itanium anyway, so all of this is really a moot point. :)
    --
    Tired of FB/Google censorship? Visit UNCENSORED!
  42. True enough by phorm · · Score: 1

    A lot of groups seem to have somewhat given up on Itanium, or at least showed it lackluster support. Perhaps as Intel improves it, Itanium may gain more popularity.

    Dell dumps Itanium

    Limited Itanium support in Vista

    1. Re:True enough by Anonymous Coward · · Score: 0

      Dell is a non-player in high-end servers, and Vista is a desktop OS. So that means nothing. Itanium sales are growing, but the midrange market as whole is shrinking.

  43. Re:why not Alpha by deKernel · · Score: 1

    The parent was talking about server chips for which the Alpha was one of the best.

  44. Spelling error by Anonymous Coward · · Score: 0

    it's spelled Iitanium in the title, it should be Itanium.

    And I get to keep my karma points wheeeeeee ^_^

    1. Re:Spelling error by Anonymous Coward · · Score: 0

      iItanium?

      Is there more to this Apple and Intel thing than they are letting on??

  45. Re:why not Alpha by BigCheese · · Score: 1

    Now we're all gonna reminisce and be sad. Thanks.

    *SNIFF* I miss the Alpha.

    --
    The obscure we see eventually. The completely obvious, it seems, takes longer. - Edward R. Murrow
  46. Re:why not Alpha by be-fan · · Score: 1

    The Alpha is only 14 years old at this point.The first was released in 1992.

    --
    A deep unwavering belief is a sure sign you're missing something...
  47. How about PA-RISC by acomj · · Score: 1

    I got a new PA-RISC machine at work. The same speed as the last one. Thanks HP!

  48. Re:why not Alpha by tomstdenis · · Score: 1

    The lag in companies like Intel and AMD is actually about 5-10 years from initial design specs to in your local store.

    There is "a lot" of testing that goes into them. So even if HP [or whatever] could get a team together today the earliest we would see a design would be 2011. By then they'd have to plan well ahead for like 45nm, at least 4 cores of OOE processors with at least 1MB of 10 cycle cache each running at at least 2Ghz etc....

    Tom

    --
    Someday, I'll have a real sig.
  49. Intel Stock Price and Itanium by BigCheese · · Score: 1

    Does anyone else out there think the only think keeping Itanium alive is that cancelling it would cause Intel's stock price to drop?

    --
    The obscure we see eventually. The completely obvious, it seems, takes longer. - Edward R. Murrow
  50. Misc by waytootired · · Score: 1

    a) Basically, no one ever used hardware-based IA-32 execution, so better to use the silicon for something else,' said Illuminata analyst Gordon Haff. 'Of course, basically no one uses software-based emulation either HP-UX uses (used?) IA-32 emulation quite a bit - the debugger whildebeest (sp?) was a IA-32 application. I wasn't aware of this fact until I looked at it. Emulation was more or less flawless.
    b) Itanium failed. It failed for many reasons. First, because it relied on compilers to generate optimal code (sequences of correctly paralellized instruction groups) to get decent performance - the world is not quite ready for this. Second, because it didn't seem to do much better than existing (Intel) processors, and thus had no reason to exit. It was a novel idea, and it was a lot of fun to play with, but ultimately more or less useless.
    c) Itanium was not targetted for the desktop PC market, although they did have desktop Itanium machines available. It was definitely not targetted for laptops (doubt it could fit in one last time I looked). It was targeted at servers and had some success in that area, though (b) above still holds.

    1. Re:Misc by waytootired · · Score: 1

      *Sigh* Note to self: type, read, post. In that order. The debugger was a PA-RISC application, emulated in software... I rest my case.

  51. Re:why not Alpha by Paul+Jakma · · Score: 3, Interesting

    I studied the alpha prior to the announcement that their new version would have out-of-order, so I don't know if they ever did go that route.

    Yep, with the 21264 - aggresively out-of-order CPU. The 21064 and 21164 might not have executed instructions out-of-order, however they were highly speculative. AXP arch was designed for out-of-order from the beginning, the two early CPUs did memory IO out-of-order. 21064 had a 32 entry register file it seems, not 2, btw, according to a paperp on the AXP 21064 I found on google written by a DECy.

    Their performance would be comparable to the AMD-64, but not much faster.

    Agreed, cause guess what: AMD64 is Alpha's progeny-in-spirit. ;)

    The AMD K7 is very alpha-like (hence so is the K8). Highly speculative, out-of-order, wide multiple issue CPUs like the 21264. Not co-incidentally given that Dirk Meyer, co-architect of the 21264, led the AMD K7 design team. K7 used the 21164/21264 EV6 PtP interconnect too. K8 made it routable with HyperTransport - just as DEC^WCompaq did with EV6 in the 21364. You would still expect this mythical equivalently developed Alpha to beat AMD64 though, given it'd be able to use the die-space 'wasted' on x86-decoding for something more productive (cache or somesuch).

    --
    I use Friend/Foe + mod-point modifiers as a karma/reputation system.
  52. how to save even more chip real estate by Anonymous Coward · · Score: 1, Funny

    Basically no one uses Itanium, so we can save even more by getting rid of the Itanium instruction set. That leaves us with the cache, and we can bolt that onto one of our AMD-clone 64-bit processors and maybe get some bucks.

  53. Re:why not Alpha by rainman_bc · · Score: 1

    why not dump Itanium compatibility and just go back to Alpha?

    Because all the old Alpha engineers now work for AMD =D

    --
    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
  54. Transitive QuickTransit by Guspaz · · Score: 1

    Software like Transitive's QuickTransit (Apple licenses it as "Rosetta") is setting new records for emulation speed due to integration with the native operating system and caching

    QuickTransit is already available with a Itanium back-end (allowing x86, MIPS, POWER/PowerPC code to run on an Itanium)... And considering the insanely high number of registers on the Itanium (16x that of the x86), emulation should be extremely fast.

  55. Nothing unusual. Most American girls breast fake by Anonymous Coward · · Score: 0


    Nothing unusual. Most American girls breast fake. Stupid girls. Yes. In Soviet
    Russia we judge women by how much hair is under arms and on legs. You can't fake that!

  56. You mean silicone, you silly con? by Anonymous Coward · · Score: 0

    lol

  57. Re:why not Alpha by aaronl · · Score: 1

    Considering that Itanium, P4, Athlon, and Opteron are totally useless for portable systems... what's your point? You don't use a 100W chip in a laptop. Intel maintains the P3 line for portables, and AMD has their own separate line of portable chips.

  58. Re:why not Alpha by aaronl · · Score: 1

    Alpha was used in everything up to supercomputers, too. You may have heard of Cray Supercomputing? They used Alpha processors.

  59. Why? by suyashs · · Score: 1

    You know why nobody uses any of that stuff? Because nobody uses the Itanium.

    --
    http://chrono.posterous.com/
  60. x86 is *needed* on Itanium by kirk.so · · Score: 4, Interesting

    The x86 was never used on itanium ? crap.
    Sure ist was ( and I assume is ) used - for the firmware. IIRC, the EFI-firmware of the Itanium boxen was entirely x86. They use the x86-ISA for running the x86-based firmware of add-on cards. That way, Itanium boxen are able to use about any PCI-card out there, without
    them having any special firmware.
    Alphas did that in software, which mostly worked but far from working with everthing.
    SPARCs and the PowerPC-based Apples have PCI, but neither is able to handle standard
    PCI-cards for exacty that reason, which is why you have to shrug off $$$ to get the same
    PCI-hardware with their native firmware support.

    Ok, any PCI-card stuffed in an Itanium box would need decent OS-drivers, but at least
    that is in the realm of the OS-vendor and drivers can be ported. Only very few
    PCI HW-manufacturers ever did anything but x86 firmware, geared towards BIOS.

    EFI, the firmware that ships with Itaniums, is quite good at handling that crappy
    PC-BIOS type firmware. Need a decent RAID-controller ? Just stuff it in.

    I'd call that a big plus. There are and have been numerous misconceptions about Itanium
    from the very beginning, but saying "Nobody needs on-chip x86" is utterly stupid.

    IIRC, the chip "real-estate" needed for x86 was in the lowish single-digit percentage
    of the total chip-real estate. And it was a good investment, since it saves $$$ for
    anybody running Itaniums. It was there for exactly that purpose, until some marketing
    freak obviously decided to sell that as "backwards compatibility". x86 on Itanium was
    and is dead slow, but for POST/Init purposes, it is sufficient.

    Please, intel, keep it. If Itanium is ever going to be a success, users will happily
    welcome the ability to extend systems using standard off-the-shelf components.

    And, while we are at it, start shipping EFI for the "x86-crowd" now. I think, i am not
    alone with the perception, that hitting "CTRL-S", "ESC whatsoever" at the right moment
    during POST to enter some firmware configuration tool of some card, just plain sucks.

    I want a firmware shell. I want x86-style SRM. EFI is close to that. Intel even
    open-sourced major parts of EFI ( www.tianocore.org ). AFAIK, the Intel-based Apples
    will use it. I want it too.

    For gods sake, keep x86 in Itaniums.

    Regards

    1. Re:x86 is *needed* on Itanium by Alioth · · Score: 1

      A major correction needed here: Many PCI cards (probably most) will work regardless of the CPU - it really depends on the card. I have a bog standard cheap USB/Firewire card in my Sun Ultra 5 (which has a 64-bit UltraSPARC II processor) and it works admirably. Network cards aren't an issue either (perhaps they can't be used to PXE boot, but the Sun's firmware can do that without needing the firmware on the network card).

    2. Re:x86 is *needed* on Itanium by kirk.so · · Score: 1

      There are of course PCI cards without any firmware at all. Those obviously don't care about the arch, they are being plugged in.

      By sheer conincidence, those are the ones that:
      1. Get integrated on mainboards anyway ( Networking, USB )
      2. are the cheapest

      Graphics boards, RAID-controllers and the like are a completely different story.
      ( No, I am not talking promise style 1.5-channel IDE-raids here ;-)

      Cheers

    3. Re:x86 is *needed* on Itanium by Anonymous Coward · · Score: 0
      boxen

      Please stop using this word.

  61. Alpha was 64-bit you nincompoop by Anonymous Coward · · Score: 0

    N/T

    1. Re:Alpha was 64-bit you nincompoop by maraist · · Score: 1

      Re:Alpha was 64-bit you nincompoop

      Umm.. no.. It had 64bit memory addressing and 64bit long-word ALU capability. The 64bit long-word ALU have very little performance pentalty over the 32bit counter-parts (all pipes/stages were wide enough to operate on 64bit data). The CPU was timed to meet 64bit delay requirements, but multiplation and friends necessarily run slower on 64 v.s. 32bit operations. Instructions were still 32bit and it was still optimized for 32bit execution. If it were optimized for 64bit execution, then, like it does for 16,8,4,1bit operations, you'd have to emulate those operations as well. The basic word was still (like in almost all modern CPU's) 32bits.

      The alpha was no more operationally 64bit than the AMD-64..

      --
      -Michael
  62. Plan ahead on bits by raftpeople · · Score: 1

    The designers of the AS400 didn't go to 2048 bits, but every address is 128 bits from day 1 for just the reason you mention.

  63. Intel Inside by Sigg3.net · · Score: 1

    Circling both nipples, in tattoed blue; Intel Inside.

    In Soviet Russia, fake tits up you.
    eh...

  64. math by Anonymous Coward · · Score: 0

    itanic - x86 - (grandeur delusions) = alpha

  65. Probably a good idea by Anonymous Coward · · Score: 0

    makes perfect sense. why cripple a new design with legacy support. no one buys an itanium2 to run legacy x86 applications. Most Itanium2 users run linux, and probably have the source code, or are buying from a vendor that will build native binaries at this end of the market.

  66. Hehe, I prted the FIRST software emu for ITANIUM ! by MajorDick · · Score: 1

    Outside of Intel that is, When intel was first developing the Itanium, without x86 compatibility originally , I was granted access to their hardware through their SDV program, I ported Bochs over, it took about 2 days with most changes being in the assy routines, it wasnt so bad, its kinda funny, as the project became a total waste as they introduced this at the hardware level.

    This whole Itanium fiasco is why I sold my intel stock and looked for other vendors, http://bochs.sourceforge.net/screenshot/whistler.j pg
    I think it was 2000 or so.....It looks good on a resume along with 100 other useless things like it....

  67. What a nice world you must live in by p3d0 · · Score: 1
    For the rest of us, the following still apply:
    1. Lots of code we want to run has no source code available. Think MS Office for instance. (Ok, who would run that on an Itanium, I know...)
    2. 32-bit code performs better for some workloads because pointers are smaller. If your data structures contain lots of pointers then you might find a substantial performance boost because the smaller pointers lead to a smaller cache/TLB footprint. (Ok, Itanium's hardware emulation was slow enough that this point wouldn't hold anyway...)
    3. Some of the best JVMs don't support Itanium, and even for those that do, see point #2.
    Yes, it makes sense to drop hardware emulation from Itanium, but not for the reasons you mention.
    --
    Patrick Doyle
    I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
  68. Aargh, forgot point #4 by p3d0 · · Score: 1

    You can't just recompile 32-bit source code and expect it to work on 64-bit hardware unless (a) you're using a wordsize-agnostic language, or (b) you have written your code very carefully with 64-bit compatibility in mind.

    --
    Patrick Doyle
    I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
  69. Cost a buttload by Anonymous Coward · · Score: 0
    640K was a whopping amount of RAM in the day. It also cost a buttload

    Is that a metric or imperial buttload?

  70. Re:Corrected Corrected headline by Anonymous Coward · · Score: 0

    Iintel Dumps Iitanium's x86 Hardware Compatibility.

    The extra "i" is for "idiot".

  71. Re:Nothing unusual. Most American girls breast fak by tetabiate · · Score: 1

    we all know the champion is Brazil, there it is really difficult to find a girl not having a fake body part.

  72. Great! About time! - but there's a boogy man... by TerryOutOfWork · · Score: 1

    One of the most significant events in computer history was IBM abandoning tubes for transistors and a new architecture for the 360 series.

    This is finally happening again. There will be a great deal of moaning about having to upgrade all the software then we will step into a great new world of higher performance!

    UNLESS - we bung the whole thing up with DRM.

    With DRM built in we will buy our computers, own our computers, pay for our computers, but they won't be working for US - they'll be working for THEM.

    This is how the very rich get very richer. Make the CLIENT pay for THEIR security.

    This can still all end in tears.

  73. This isn't even news... by Anonymous Coward · · Score: 0

    Intel announced this over a year ago.

  74. Something about the writing style is familiar by Paul+Crowley · · Score: 1

    "You don't need to be a Kreskin to predict Itanium's future. The hand writing has been on the wall since at least December 2004, when Hewlett-Packard handed over development and ownership of the Itanium platform to Intel. Soon after, vendors including IBM, Microsoft, and Dell began withdrawing their support for the Itanium processor.

    Let's keep to the facts and look at the numbers.

    # Chip speed of 1.6 GHz, down from the originally expected 2.4 GHz
    # Front side bus speed of 400 MHz, down from 667 MHz
    # On-chip Level 3 cache, down from 24 MB (12 MB per core)
    to an undisclosed number

    All major surveys show that Itanium has steadily declined in market share.

    Fact: Itanium is dead"

    1. Re:Something about the writing style is familiar by drinkypoo · · Score: 1

      Soon after, vendors including IBM, Microsoft, and Dell began withdrawing their support for the Itanium processor.

      Let's keep to the facts and look at the numbers.

      Yeah, let's look at the numbers. Three of the most important computer-related companies on the planet dropped itanic. That's a good number to consider :)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  75. The real reason is AMD64 by Ed+Avis · · Score: 1

    They'd have to rework the i386 compatibility anyway to handle AMD64 instructions. And it would be a real embarassment to have two 64-bit processors on the same die (the failed one and the successful one).

    Perhaps it would be easier for Intel to just ship a Xeon processor supporting the AMD64 instructions, and do the Itanic support as a software emulation.

    --
    -- Ed Avis ed@membled.com
  76. UR right! by PaulBu · · Score: 1

    The whole Itanium story made me do a slip about HP involvement... Of course it was Apple! ;-)

    Paul B.

  77. BJ Advice by Anonymous Coward · · Score: 0


    Everyone I've ever given head to (a LOT of people) says its the best they've ever had. Well guys this is why, so try and make your man happy.

    1.I LOVE to do it. It absolutely turns me on more than recieving it. I get a massive stiffy, sometimes I even shoot my load, without masturbating.

    2.I look up at him while I'm doing it so he knows I'm loving it. You give him the eyes or that "i fucking love this" face. Literally devour him. Act like you can't get enough of his cock.

    3.I spend a lot of time licking and sucking his balls while using my hands on him and looking him in the eye... Also--yes I'll perform a "hummer" if you will

    4.Of course I SWALLOW.. but I also allow him to pull back, jerk into my open waiting mouth and onto my chest and six-pack.

    5.I always give while on my knees.. He's either standing up over me holding my head or he might be sitting on the couch, or toilet.

    6.Yes, I have let him give me a pearl necklace. In that case I wipe the cum off of my neck and I have him feed it to me off of his fingers.

    7.I'll talk dirty to him a little bit. Tell him I don't want him to cum yet because I'm not ready, or that I love the way his hard cock feels in my mouth.. I take my time--he better be prepared to sit there for at least a half hour probably more.

    8.I love to lick and tickle under his balls. The "taint" if you will. Or I'll use my thumb to apply light pressure in circular motions or going up and down. I'll go lower and lower down to the ass if he lets me. If he's enjoying it, yes I will rim, and yes I have fingered his ass.

    9.When I'm getting really turned on, I'll stroke my cock and finger my asshole in front of him. Then I'll take my fingers rub my pre-cum on his head and then suck it off. I'll also suck my fingers clean for him. If its someone who paid me or something then I've even gone so far as to climb onto him, slowly guiding his cock into my ass.. sit there for about 10 seconds then get back down on my knees and continue sucking.

    10.I deep throat. There have been instances where I dont even realize he came because it's so far down my throat. If he gags me I keep going.

    11.And its just general technique. I have a very busy tongue and I get him into a great rhythm building him up and slowing down to help prolong and intensify his orgasm. I love to flick my tongue back and forth around his sensitive ridge and all underneath it.

    12.I also SUCK his cock head firmly letting it pass in and out of my mouth, so my lips run over him while he fucks my wet mouth.

    13.I'll get him nice and wet and use my hand to stroke him in a counter-clockwise motion and then I suck on him going clockwise. The other hand goes to his nipples, balls, asshole, etc.. but the combined sensations get him so hard.

    14.When he's ready to cum thats when speed and intensity HAVE TO INCREASE. I bob up and down on him faster and faster and I let him thrust his hips too so I take him even deeper.

    15.After he cums I'll continue to suck him slowing down intensity and speed, bringing him down from his orgasm until he stops me becuase he's so sensitive.

    And that is why I give head like a pornstar. No, I am not a slut and I do not have STD's. I'm just a guy who likes to suck cock. Men--there are other men out there like me so don't give up hope if you have never had great head.