Slashdot Mirror


Is Prescott 64-bit?

unassimilatible writes "According to The Inquirer, Intel's new Prescott has 64 bit instructions lurking inside. Could really rain on the parade of those who thought the new Athlon 64's would be supreme - especially when you look at Intel's price roadmap. Don't run out and buy an Athlon 64 just yet..."

487 comments

  1. Hrmm by acehole · · Score: 4, Funny

    I haven't even run out and bought a 32bit. Contiki and c64 1mhz 8bit power keep me warm at night.

    --
    Be you Admins? nay, we are but lusers!
    1. Re:Hrmm by squiggleslash · · Score: 4, Insightful
      According to El Reg, Prescott really will keep you warm at night. 100W power dissipation... mmmmms :)

      (To put that into perspective, the twin G5s in Apple's PowerMac together put out 90W total.)

      --
      You are not alone. This is not normal. None of this is normal.
    2. Re:Hrmm by stilwebm · · Score: 4, Funny

      According to El Reg, Prescott really will keep you warm at night. 100W power dissipation... mmmmms :)

      An Easy Bake Oven uses a 100W incadescent light bulb as the heating element. So with a heatsink and a fan, does that make a case with Prescott Inside an Easy Bake Convection Oven?

    3. Re:Hrmm by Anonymous Coward · · Score: 0

      > Contiki and c64 1mhz 8bit power keep me warm at night.

      That wouldn't cut it up here in Wisconsin. I appreciate the glowing warmth of an Athlon to keep me warm during those long winter nights. If only the damn thing would stay running more than an hour at a time I might be able to use it for something productive. Intel to the rescue!

    4. Re:Hrmm by Anonymous Coward · · Score: 1, Insightful

      For most of the 90s intel didn't really have a competitor. But if the chips never get faster who is going to upgrade?

      Competition lowers prices, there's no guarantee that it will effect innovation.

    5. Re:Hrmm by Groo+Wanderer · · Score: 2, Informative

      According to Le Inq, Prescott takes more than that.
      http://www.theinquirer.net/?article=11588
      Now these may have been taken from a roadmap that I really should not have seen, but you can see that the 100w number is a bit conservative. The next few generations are specced to narrow the gap between min and max power usage, but not lessen it. Depressing.

      -Charlie

    6. Re:Hrmm by abe+ferlman · · Score: 1

      Now with thermal paste icing!

      --
      microsoftword.mp3 - it doesn't care that they're not words...
    7. Re:Hrmm by VikingBerserker · · Score: 2, Funny

      Now I know what my next case mod will look like. Thanks!

    8. Re:Hrmm by Anonymous Coward · · Score: 0

      Question... why is processor bit-ness always in powers of two?

    9. Re:Hrmm by cookd · · Score: 1

      Are you serious or trolling?

      --
      Time flies like an arrow. Fruit flies like a banana.
    10. Re:Hrmm by ubugly2 · · Score: 1

      find a way to shoehorn it into an imac case it it would look just about right..

    11. Re:Hrmm by Anonymous Coward · · Score: 0

      There are 10 types of people in this world.

      Those that understand binary...

      You know the rest.

    12. Re:Hrmm by pacc · · Score: 1

      Just a pipe through the heatsink will make your computer a perfect coffee machine.

      "While making coffee [your prescott computer] will give you 25% more raw performance to be able to evaporate the water."

      What a killer application...

    13. Re:Hrmm by Fweeky · · Score: 1

      I thought it was 97 watts each.. maybe it was total; anyone have a reference?

    14. Re:Hrmm by squiggleslash · · Score: 1

      I can't find a direct link, only indirect ones. This article at IBM's site quotes 42W for 1.8GHz operation. While, obviously, it will be disproportionally higher at 2GHz, it will certainly be closer to 42W than 97W...

      --
      You are not alone. This is not normal. None of this is normal.
    15. Re:Hrmm by jonadab · · Score: 2, Informative

      You don't upgrade to get a faster CPU. Not these days. You upgrade
      for other reasons -- your old motherboard is maxed out for RAM, and
      you need more. Your old motherboard is USB1.1 and you want 2.0. You
      could get an expansion card, but you've only got one slot left and you
      really wanted to add IEEEwhateverthenumberisforthattrademarkedbus.
      The new board supports SATA RAID, which will give you a performance
      boost for disk-intensive applications. And so on and so forth.

      Do you go for a faster CPU while you're upgrading? Well, sure.
      Nobody wants to buy a new computer with the same MHz number as the
      old one, for psychological reasons if nothing else. But unless you
      raytrace animations for a living or something, it's probably not the
      thing driving you to upgrade.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    16. Re:Hrmm by pmz · · Score: 1

      100W power dissipation

      100W for one year (8760 hours) is 876 KW/hours.

      At $0.07/KW/hour this is about $60 per year in consumed electricity for a computer left on 24/7.

      While the fact that a single-CPU PowerPC or UltraSPARC-based system, for example will save you $30 or $40 per year relative to Intel's offering may seem small, consider the fact that this translates to upwards of $500,000 for a 1000-PC company per year.

      Intel's latest CPUs really are a drain on the economy for dubious improvements in performance for most users (movie making ray tracing niche dwellers need not replay). People really should consider the low-power alternatives (sub 20 watt CPUs) for productivity desktops. Also, not only do they use less power, they cost less up-front, too.

  2. Re:I wouldn't buy the Athlon anyway by coene · · Score: 1

    Several - including one in my laptop. Too bad about your luck, I haven't had any problems.

  3. Re:I wouldn't buy the Athlon anyway by Anonymous Coward · · Score: 0

    I've had much better experiences with AMD to Intel. Longer lasting, better performance, etc

  4. FUD by Anonymous Coward · · Score: 4, Insightful

    Intel, those typical insensitve clods, are spreading FUD around to kill AMD.

    1. Re:FUD by javiercero · · Score: 5, Interesting

      This is no flame bait, it is Intel's business practice. They have done it over and over and over, if any of you were alive during the 80's you'd know about intel's 32bit move with the 386 which took forever to come out, meanwhile... other people released 32bit solutions, mostly NS and Motorola. Intel's FUD machine went into high gear and told customers to hold on since the 386 was going to be out any day then and was going to be the best processor ever. So better processors that were years ahead of the 386 got killed that way.

      In the 90s Intel did the same with the Pentium and the R4000s that were going to be the basis for the ARC platform. Intel said that the Pentium was going to be out any day then and it was going to run circles around the RISC machines. The pentium was at least 4 years late and was well behind RISC offerings in performance. But Intel managed to kill the ARC consortium.

      This is the latest in Intels FUD campaign, maybe it is time to break the circle... buy intel and have 64bits TODAY... screw them, with their "ooooh we may have a surprise for you" and all that nonsense.

    2. Re:FUD by MarcoAtWork · · Score: 2, Funny

      buy intel and have 64bits TODAY

      you did mean AMD, didn't you? or maybe intel's marketing is so good that it made you change your mind halfway through your post :)

      --
      -- the cake is a lie
    3. Re:FUD by DarkEdgeX · · Score: 1

      Intel does have 64-bit today, it's called Itanium, and it has performance that blows away x86-based CPU's.

      The problem of course, is the whole chicken and egg scenario. Not enough "must have" software is targetted towards it. Not until you can buy IA-64 editions of Photoshop, Office, and other "killer apps" will it become a must have in itself.

      This type of problem has plagued every major technology platform, from Windows vs. MacOS, BeOS and Linux, to game platforms, and so on.

      --
      All I know about Bush is I had a good job when Clinton was president.
    4. Re:FUD by mauriceh · · Score: 1

      Absolutely. This is a TOTAL TROLL!

      --
      Maurice W. Hilarius Voice: (778) 347-9907
    5. Re:FUD by Anonymous Coward · · Score: 1, Insightful

      no he is saying that "buy intel and have 64bits TODAY" is the message that Intel is trying to tell its consumers

    6. Re:FUD by Tailhook · · Score: 1

      screw them, with their "ooooh we may have a surprise for you" and all that nonsense.

      No, screw you and your simple minded conspiracy theories. Screw your distain for the success that is Intel.

      Intel rules because Intel makes computing real for the largest available market. Not just the ivory tower academics and industry pundits, but everyone that needs to compute.

      Exotic playthings like MIPS, Next and Alpha play the role of the Duesenbergs and Bugattis of another era. Intel is our Ford. You might not like having to spend your life surrounded by computing's moral equivalent of Fords, but that's how it is; get over it or go elsewhere for air rare enough to suit your "taste."

      Intel isn't going to let AMD cannibalize the low end of the 64 bit market. No way in hell. They're too smart for that and they'll do what they must to retain their market. When the grown-ups at Intel figure out that x86 needs 64 bits of address space the long-hairs will swallow their egos, shuffle back to their desks and make it so.

      Oh, and you? You might just find yourself parked in front of one for the next 15 years, whether you like it or not.

      --
      Maw! Fire up the karma burner!
    7. Re:FUD by javiercero · · Score: 1

      So basically you are telling me to eat feeces since 10 billion flies can not be wrong? Oh jeez speaking of simplistic views.

      I was just reporting on Intel's FUDs practices which are well documented, in fact IBM's FUD in the 60/70s was enhaced to perfection by Intel in the 80/90s. Those are well documented, if you have proof of the contrary please let us know, rather than use the oh so complex personal atack and diminish facts as conspiracy theories. LOL!

      And please do not try to use the car analogy, it just plain doesn't work. There are at least 10 car manufacturers which offer commodity cars.

      And those "playthings" are what push the envelope and give us change and advances in computing, if it was up to intel we would still be using 8088's running at 10Mhz and priced at $500.00 each. Afterall why would the change if there was no other competitor (or how you put it: plaything) around? Hadn't been for NeXT that web browser you are using to spew would have not been even invented. Had not been for MIPS probably RISC techniques would have been an academic curiosity, and had not been for Alpha and the core engineering which Intel has routed towards the Itanium team, the Itanic would be still in the drawing board.

      But by all means, god forbid anyone say anything bad about your beloved intel.

    8. Re:FUD by Wolfrider · · Score: 1

      --I was going to mod you up, but instead I'll agree with you. Posting the article with "Don't run out and buy AMD just yet..." struck me as being blatantly anti-AMD. :(

      --Slashdot should be more careful. I read that Inquirer so-called "news" article, and it seemed like just a bunch of rumours.

      --I for one have to applaud AMD's work on the 64-bit stuff, and wish them the best. Competing with Intel is not easy.

      --
      .
      == WolfriderV6 == I'm willing to admit that *I just might* be wrong... Are you??
    9. Re:FUD by cbreaker · · Score: 2, Insightful

      "And please do not try to use the car analogy, it just plain doesn't work. There are at least 10 car manufacturers which offer commodity cars."

      Well, maybe he's proving your point with his Ford analogy, even though he doesn't realize it. Ford may have been the biggest car manufacturer at one point, the leader, the only choice. But times change, and like you said, there's true competition and choice now in the car market.

      Let us hope that Intel's "Ford years" are nearing an end as well.

      --
      - It's not the Macs I hate. It's Digg users. -
    10. Re:FUD by Jungle+guy · · Score: 1

      It surprises me that Slashdot accepts this kind of nonsense. Officialy Intel says 32 bits and big megahertz for desktops is just fine, and AMD-64 doesn't cut a slack. It looks that, off-the record, someone is telling The Inquirer to wait for their next big processor. By no means I am pro-Intel or Pro-AMD (my two last processors were Intel's and my next will be AMD), but, when you want to buy a new computer today, don't get fooled by these declarations. It is a very safe bet to say that next year's processors will be faster than today's, but if you follow this logic you would postpone your buying forever!

    11. Re:FUD by thisgooroo · · Score: 1
      And please do not try to use the car analogy, it just plain doesn't work.

      actually, it does work, though not as intended: ford generally has pretty buggy cars (at least in my experience), and intel's reputation with their earliest releases isn't exactly shining (286 never really working in its "native" mode, early 387 floating point problems, the infamous pentioum (or was it 486?) floating point bug)

    12. Re:FUD by aminorex · · Score: 1

      No, screw you and your astroturfing. Screw your
      disdain for the superiority of architectures that
      can't run CP/M-86. Intel is going to get their
      lunch eaten by x86 because its faster * cheaper,
      and beats them at their own back-compatibility game.

      I'd give Intel 15 years before its out of the
      desktop CPU business.

      --
      -I like my women like I like my tea: green-
  5. It would almost have to follow AMD's conventions by Phosphor3k · · Score: 5, Interesting

    Or there will be virtuly no software for it when it comes out and for months to come. AMD has had books on the x86-64 instruction set for years now. Not to mention emulators have been available for almost as long.

  6. I would... by TWX · · Score: 5, Insightful

    "I'll stick with Intel, thanks. Any of you guys actually have a *good* AMD processor?"

    My 450MHz AMD K6-2 worked fine, at 4.5x100MHz, my 1.2GHz Athlon Thunderbird worked fine, and my Athlon XP2400+ (2.055 GHz after some interesting bus overclocking) works just fine.

    I've never had a problem with them. Do you know what you're doing? Setting the voltage levels is required on the older boards, and that actually means reading the provided motherboard manual.

    I'm looking forward to a dual-AMD 64 bit configuration for home at some point, it looks pretty sweet.

    --
    Do not look into laser with remaining eye.
    1. Re:I would... by kdsolutions · · Score: 0

      /me has a 550Mhz athlon. runniing strong for 4 years now. w00t!

      --
      Error 666 - Satanic SCO code found in your Linux kernel.
    2. Re:I would... by jesco · · Score: 1

      My old K6/200 runs happily at 250 Mhz (2,5*100Mhz instead of 3*66Mhz), and I even lowered the core-voltage to reduce heat-emission. Now *that* was some serious overclocking! :)

    3. Re:I would... by Solosoft · · Score: 1

      I have a Pentium 166MMX and it's been running fine since 1999 (when I got it). One time for fun I compiled 60 milllion digits of pi on it ... and it was perfectly fine. Also another good CPU is my PII 350 , it's been running fine since 1998 and ive never had a single problem with it

    4. Re:I would... by kdsolutions · · Score: 0

      Yes, but has yours been drop-kicked 30 feet across a room? Killed the 20GB harddisk (Maxtor, the 10GB disk, a year older, Western Digital survived just fine - stated both to indicate the force of the kick and to advocate what I feel is a more reliable name in data storage) but the CPU and mobo are both still fine to this day.

      BOO-YAH, INTEL, BEAT THAT! Throw your shit 30 feet across the room into a trash can!

      --
      Error 666 - Satanic SCO code found in your Linux kernel.
  7. Re:I wouldn't buy the Athlon anyway by Dr.+Descartes · · Score: 1

    My Athlon has run for two years now without fail for me. It's a desktop computer not a laptop so I can't relate on that respect. There were stability issues until I stopped using Win 2K and switched to Slackware. I'm not quite an AMD fanboy but they've never given me reason to purchase anything else...yet.

  8. The tide is turning for AMD by dankdirk77 · · Score: 5, Insightful

    This is a disaster for Intel, and if you follow along, HP, which is trying to sell Itanium solutions to counter IBM. I love big blue and AMD, so I can't say I'll shed a tear.

    --


    SCO: 800-726-8649
    Verisign: 800-361-8319, 888-642-9675
    Diebold: 800-433-VOTE (8683)
    1. Re:The tide is turning for AMD by Anonymous Coward · · Score: 0

      Why's it a distaster? They'll be in worse shape if they keep trying to pimp the Itanium, a chip that even after several generations of updates nobody wants.

    2. Re:The tide is turning for AMD by exhilaration · · Score: 1
      What HP calls the "Itanium" is simply the next generation of its PA-RISC processors. When Intel was shopping around for a 64-bit processor, they went to HP which already had a kickass enterprise processor. A few billion dollars later, everyone seems to believe that Intel invented Itanium, which is nothing more than a slightly souped up and rebranded PA-RISC.

      I wish people would stop comparing Intel's Itanium products with those of HP. HP's SuperDome line, arguably the best UNIX servers for serious business use, have nothing to do with Intel's "Itanic".

    3. Re:The tide is turning for AMD by Anonymous Coward · · Score: 0

      ???

      I spent a lot of time writing PA-RISC assembly in the distant past, and I occasionally have occasion to write IA-64 assembly now.

      The differences FAR outweigh the similarities.

      PA-RISC is more similar to Power4 than it is to IA-64.

  9. Great!! by Daath · · Score: 4, Funny

    I'll be able to afford it, and then run a thirty-two bit extension and GUI shell to a sixteen bit patch to an eight bit operating system originally coded for a four bit microprocessor and sold by a two-bit company that can't stand one bit of competition, on a sixty-four bit processor!
    Uhm... Maybe I'll buy it and install linux on it, all the big good games are coming to linux now it seems :) Can't wait! 178$ - wow! :)
    Doubt that I will totally be rid of windows in the next few years though. You know. Work and such ;)

    --
    Any technology distinguishable from magic, is insufficiently advanced.
    1. Re:Great!! by Anonymous Coward · · Score: 0

      I salute you and your witty command of the english language!

    2. Re:Great!! by asadsalm · · Score: 2, Funny


      GUI Extension = 32 Bits
      Patch = 16 Bits
      O/S = 08 Bits
      Coded For = 04 Bits
      Company = 02 Bits
      Competition = 01 Bit
      -----------------------
      Total = 63 Bits

      There you go! You certainly need a 64 Bit processor to run that, and you get a Bit to spare !

    3. Re:Great!! by Anonymous Coward · · Score: 0

      Oh come on, alteast come up with your own funny quote instead of stealing it from somebody else . .

    4. Re:Great!! by Anonymous Coward · · Score: 0

      thirty-two bit extension and GUI shell to a sixteen bit patch to an eight bit operating system originally coded for a four bit microprocessor and sold by a two-bit company that can't stand one bit of competition

      I still think this would be wittier if it were actually accurate. :6

    5. Re:Great!! by TomV · · Score: 1

      ... and the 1-bit power switch on the front makes 64! :-)

      TomV

    6. Re:Great!! by Anonymous Coward · · Score: 0

      -1, old

  10. Re:I wouldn't buy the Athlon anyway by Anonymous Coward · · Score: 0

    I'll stick with Intel, thanks. Any of you guys actually have a *good* AMD processor?


    uhm, I do, troll. Two of them in fact.

  11. Let me see if i can understand this by Disevidence · · Score: 4, Interesting

    The "Prescott" has 2 32 bit cores, but the "secondary" core is missing an AGU, among other things, and this is pointing to the fact that most Prescotts have some sort of 64 bit functionality in them, but their keeping their lips shut about it?

    So it seems to me that possibly Intel are waiting to see how AMD's 64 bit chip goes, and if its going better as a 32/64 bit chip then Intel's Itanium, release their Prescott with "fully" added 64 bit functionality?

    Am i correct in my logic? I can't really follow why they're keeping tight about it.

    --
    Think nothing is impossible? Try slamming a revolving door.
    1. Re:Let me see if i can understand this by TWX · · Score: 1

      Perhaps they needed a chip *now* and their Prescott chip wasn't really where they wanted, so they're releasing it as a 32 bit chip...

      Remember, a lot of OEMs use Intel processors exclusively. So, Intel's not having a solution that AMD has had available for testing and now for production for a cheap price is egg on the face of Intel. If they get the "Prescott 32 bit" chips to be successful, then when they get the "Prescott 64 bit" chips to market, the name will have already established itself.

      Who the hell names their chip after a town in Northern Arizona anyway? Sheesh.

      --
      Do not look into laser with remaining eye.
    2. Re:Let me see if i can understand this by cbiltcliffe · · Score: 1

      Remember, a lot of OEMs use Intel processors exclusively.

      A lot? I thought Hell^H^H^H^H^H Dell was the only OEM that was exclusively Intel.... Am I incorrect?

      --
      "City hall" in German is "Rathaus" Kinda explains a few things......
    3. Re:Let me see if i can understand this by javiercero · · Score: 1

      Intel names products after geographic places in their production/design states. Hence most of the products so far have been named after North Western rivers and landmarks, I guess they are moving over their Arizona production/design plants in the naming scheme now.

    4. Re:Let me see if i can understand this by xswl0931 · · Score: 4, Insightful

      Assuming it's true that Prescott has 64-bit capabilities built in but not enabled, the reason to keep it secret is to not have a cheap Intel 64-bit capable processor cannibalize their expensive Itanium sales. If a dual or quad proc Prescott 64-bit system costs the same as a single proc Itanium system, which would you buy?

    5. Re:Let me see if i can understand this by IM6100 · · Score: 1

      Is this going to be another Celeron 300 thing?

      (everybody bought Celeron 300's, and overclocked them, instead of buying expensive Pentium II's, back in the day)

      --
      A Good Intro to NetBS
    6. Re:Let me see if i can understand this by hawkbug · · Score: 1

      Yes, I believe you are. From what I understand, Gateway and IBM are also Intel only shops now. Gateway used to sell AMD boxes, but gave that up a few years ago due to market pressure, and I'm sure massive Intel discounts.

    7. Re:Let me see if i can understand this by CAIMLAS · · Score: 3, Funny

      "back in the day"? You must be, what, 15, 16?

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    8. Re:Let me see if i can understand this by IM6100 · · Score: 1

      'back in the day' refers to Internet time.

      My first home computer was a TRS-80 model 1. I bought a TI SR-56 programmable calculator because that was all I could afford back in 1977. My first programming courses in High School were on Teletype ASR-33's with dial up 300 baud modems to an HP Mini timesharing system.

      'Back in the day' I went to tours on 'Family day' (I'm an IBM brat) and got the infamous 'Snoopy' poster in ASCII art, and got to actually see and touch 'real' computers like Model 360's. But that was, oh, about 1970, when the only computer I owned was a plastic DIGI-Comp 1. Back then I wanted to own my own oscilloscope. Wanting a computer was later, when I read a construction article about one made using transistors for flipflops and a telephone dial as the input device (yes, just a discrete-parts binary 'adder' but we thought of them as 'computers' back then)

      --
      A Good Intro to NetBS
    9. Re:Let me see if i can understand this by sjwt · · Score: 1

      goto love ppl who add too many or too few
      ^H

      --
      You have 5 Moderator Points!
      Which Helpless Linux zealot/MS basher do you want to mod down today?
    10. Re:Let me see if i can understand this by Mr.+Frilly · · Score: 1

      IBM's due to release an Opteron workstation next year...

    11. Re:Let me see if i can understand this by WalksOnDirt · · Score: 1

      Five was the correct number of ^H's. Only four would have left two spaces in a row.

      --
      a,e,i,o,u and sometimes w and y (at be if of up cwm by)
    12. Re:Let me see if i can understand this by Anonymous Coward · · Score: 0

      Props.

    13. Re:Let me see if i can understand this by hawkbug · · Score: 1

      That's good news - I generally like IBM, but until I get can get a new thinkpad with an AMD cpu in it, I'm not buying a new one.

  12. Re:BAH! 286 is all you need. by placeclicker · · Score: 1

    I dont know about you, but 640K is good enough for me.

    --

    Browse at -1, because trolls are often the most creative part of /.
  13. Re:I wouldn't buy the Athlon anyway by NanoGator · · Score: 3, Insightful

    "I'll stick with Intel, thanks. Any of you guys actually have a *good* AMD processor?"

    Yes. Both my machine at work and at home are dual Athlons. Not only do they work great, but they also were very good price wise. On top of that, Lightwave (3d Rendering App) competes very nicely with the P4s, though LW is heavily optimized for Intel.

    I'm not an AMD zealot, but I guarantee you that if I had the problems you did, my AMD'd be in the trashcan in a heartbeat. I can't afford aborted renderings.

    --
    "Derp de derp."
  14. IInntteerreessttiinng by Eponymous+Cowboy · · Score: 5, Funny

    II aamm rruunniinngg aann eevvaalluuaattiioonn PPrreessccootttt rriigghhtt nnooww,, aanndd II aamm nnoott ppoossiittiivvee,, bbuutt II tthhiinnkk tthhee eexxttrraa bbiittss mmaayy nnoott bbee iinnddiivviidduuaallyy aaddrreessaabbllee,, bbuutt aarree jjuusstt uusseedd ffoorr rreedduunnddaannccyy..

    --
    It's hard for thee to kick against the pricks.
    1. Re:IInntteerreessttiinng by gonk · · Score: 1

      I wish I had mod points left....!

    2. Re:IInntteerreessttiinng by Waffle+Iron · · Score: 5, Informative

      You're guess is basically on the right track. I don't want to violate any NDAs, but let me just say that the AAA and AAS opcodes will now support Unicode.

    3. Re:IInntteerreessttiinng by Waffle+Iron · · Score: 1

      s/you're/your/

    4. Re:IInntteerreessttiinng by Waffle+Iron · · Score: 5, Funny

      Ok, ok, people. +5 informative... Thanks, but it was supposed to be a stinkin' joke. I guess nobody remembers what the AAA and AAS opcodes do. (They were introduced around the 8080-era and not much used since. Hint: A is for ASCII.)

    5. Re:IInntteerreessttiinng by Anonymous Coward · · Score: 0

      Ah, thanks for the explanation, I couldn't wrap my head around it.

      Slashdot Rule of thumb : don't make technical joke, you wouldn'd get moderated funny, but 'informative' (if lucky) or at worst 'troll'.

    6. Re:IInntteerreessttiinng by Anonymous Coward · · Score: 0

      I'd write a long BCD is dying post here but I don't have a template handy.

    7. Re:IInntteerreessttiinng by Anonymous Coward · · Score: 0

      You are looking for this, I believe.

    8. Re:IInntteerreessttiinng by kasperd · · Score: 1

      You are looking for this, I believe.

      Nice, now I can get the news I'd like to hear.

      --

      Do you care about the security of your wireless mouse?
    9. Re:IInntteerreessttiinng by EpsCylonB · · Score: 1

      Wow, thats gotta worry you a little when even the geeks on slashdot don't understand you.

    10. Re:IInntteerreessttiinng by Molt · · Score: 1

      A is for ASCII, and so AAA is for ASCII ASCII ASCII? So good they named it thrice?

      --
      404 Not Found: No such file or resource as '.sig'
    11. Re:IInntteerreessttiinng by Anonymous Coward · · Score: 1, Insightful

      Not only I don't remember what it is - I also don't have a clue what your joke was.

      AAA - Adjust after add

      AAS - Adjust after sub

      ??? wtf? ???

    12. Re:IInntteerreessttiinng by Deslack · · Score: 0

      AAA: ASCII Adjust for Addition.

      --
      .sigs are useless; it doesn't protect you from imposters.
    13. Re:IInntteerreessttiinng by Waffle+Iron · · Score: 1
      AAA = ASCII Adjust after Add
      AAS = ASCII Adjust after Subtract

      They are for binary coded decimal math; they allow you to directly add numbers encoded in the ASCII characters '0' to '9'. If you add two such values into the AL register, the carry flags and the AH register are adjusted if there was a carry past the value 9 to prepare for adding the next digits.

      To do a pointless thing like updating these instructions to support Unicode, these opcodes would need to be extended to use 16-bit registers.

    14. Re:IInntteerreessttiinng by Anonymous Coward · · Score: 0

      Your cleverness is wasted here.

      Though I must say your post is far funnier than the one you attached it to.

  15. Wow! Not. by Anonymous Coward · · Score: 5, Insightful

    Hey! There's a rumour that Intel might have not bothered marketing their new developments properly. You should ignore what is on the market and working just in case you can tweak a future chip to get something a bit like it. You heard it here first!!!

    Idiot.

  16. This is pure speculation by dzym · · Score: 4, Insightful
    From The Inquirer, the The Register wanna-be no less.

    The allegedly informative statement is couched in so many conditionals that they of course can once again squirm their way out of any uncomfortable spot they might get stuck in.

    Plus, I don't see Microsoft supporting not one but TWO Intel-specific 64-bit platforms.

    Hold on to your Athlon64 pre-orders, boys and girls.

    1. Re:This is pure speculation by Disevidence · · Score: 1

      Read the inquirer article, there are 2 links to other articles outlining why there is possible 64 bit functionality in the chips. The 2 linked articles (from Chip Architect) show with facts and logic why there could be (or is) 64 bit functionality in the Chips.

      It might be fud, but there ARE facts there.

      --
      Think nothing is impossible? Try slamming a revolving door.
    2. Re:This is pure speculation by Keeper · · Score: 1

      Plus, I don't see Microsoft supporting not one but TWO Intel-specific 64-bit platforms.

      If the platforms both become popular they will. Having .Net out there actually makes supporting two 64bit platforms pretty easy. Most of the work is creating two separate JIT compilers...

    3. Re:This is pure speculation by Anonymous Coward · · Score: 0

      From The Inquirer, the The Register wanna-be no less.

      Actually it is run by an ex-Register writer, so it is basically the real thing.

    4. Re:This is pure speculation by Anonymous Coward · · Score: 1, Insightful

      Uh, no.

      Most of Windows/Office/etc is not written in C#/.Net, yet. If we had operating systems running on JIT, woah.... well, just look at Sun's failed attempts at true java OSes.

    5. Re:This is pure speculation by mauriceh · · Score: 2, Informative

      Mike Magee STARTED The Register, and still owns part of it.
      He left due to an internal disagreement and started The Inquirer.

      Get som facts before you babble my friend!

      --
      Maurice W. Hilarius Voice: (778) 347-9907
    6. Re:This is pure speculation by TheLink · · Score: 2, Insightful

      Well so far in my experience The Inquirer's pure speculation has been a lot more accurate than tons of other news sources.

      Especially when it comes to info technology.

      They often get the scoop on things well before anyone else does. It's useful to know about things before they happen.

      --
    7. Re:This is pure speculation by ZaPhOd42 · · Score: 1
      "From The Inquirer, the The Register wanna-be no less."

      Ummm, The Inquirer was set up by Mike Magee who originally set up The Register.

      Apparently he had some sort of major falling out with another Register founding member and went off and created The Inquirer.

      So, The Inquirer is hardly a "Register wanna-be" is it?

    8. Re:This is pure speculation by Anonymous Coward · · Score: 0
      But its well known that VS.Net is writen in .net, the current leaked version of longhorn features a managed code (.net) shell.

      Office 11 (2003) appears to be a hybridised .net/native application.

      Given a year or two I can't see why MS couldn't transision to a totally .net centric application base. Remeber .net doesn't have to be JIT'd you can make a .net compilier nativise IL for the target platform. Then ship only the native binary.

  17. I've never bought Intel by RichiP · · Score: 5, Interesting

    Since 1997, all my machines have been AMD's. The K6-2 is still alive, actually. One of them (a Duron 600) has been running 24x7 for the last 3 years. My gaming rig's a dual Athlon MP2000+. My current workstation's an Athlon XP2400+. I've NEVER had any problems with them, either hardward or software (Linux).

    My biggest problem is what to do with the old mobos and processors that I put aside due to upgrading.

    No, I've never had a reason to spend more for so little (it's even arguable whether you get more for spending more ... I know. I've administered Intel-based servers).

    1. Re:I've never bought Intel by ScrewMaster · · Score: 1

      A long time ago, there was a reasonable argument that one should buy Intel to avoid compatibility problems (although those were mostly due to Cyrix issues.) I also run four AMD systems at home (my server is a 1.4 Ghz. Athlon that has never crashed, not once) and have no problems. My only Intel is an old Toshiba laptop that I use for playing MP3s. At work they gave me a 2.8 Ghz. Pentium IV Compaq and its a pain in the neck. Slow and flaky, although that's more Compaq's fault than Intel's.

      --
      The higher the technology, the sharper that two-edged sword.
    2. Re:I've never bought Intel by CAIMLAS · · Score: 1

      "me too!"

      I recall when I was able to afford, and purchased my own system (K6-2 233MHz, baby! raw powerrrr!), that many of the people I knew that used Intel hardware said I would encounter stability problems. I never did (as a result of the processor). I had some memory die, but that was it.

      They also claimed that their performance was better (on idenically clocked/marketed 233MHz systems). On quite a few occasions I was able to prove them wrong by being able to functionally run programs they couldn't. The other hardware was quite similar, too. Not sure I understand why it worked that way (due to the limitations of the K6-2), but it did, despite all logic.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    3. Re:I've never bought Intel by Anonymous Coward · · Score: 0

      I have good experience with AMD processors as well.

      My biggest (fairly recent) complaint is that only the MP motherboards support ECC.

      That really sucks, and not just because of random memory errors, but it can be difficult to determine if you have bad RAM unless you have ECC. I've had bad RAM that memory testers didn't complain about.

    4. Re:I've never bought Intel by Bobke · · Score: 1

      Not quite impressive, my router is a pentium 166 MMX and it has been running continuously since 1997, overclocked to 225Mhz (bus from 65 to 72 && cpu from 166 to 200.

    5. Re:I've never bought Intel by vadim_t · · Score: 1

      Question: Why do you use a dual Athlon MP for gaming? I'm tying this from one, but it doesn't help much with games. It's great for compiling code, and Gentoo, but doesn't improve games much. So, why aren't you using the XP2400 for games?

    6. Re:I've never bought Intel by Hoser+McMoose · · Score: 1

      One of the really nice bonus off-shoots of the new Athlon64 and Opteron processors with their on-die memory controllers is that ALL of these systems will work with ECC memory (assuming the motherboard manufacturer's don't go way out of their way to try and screw this up).

    7. Re:I've never bought Intel by Arker · · Score: 1

      While I most agree with you, and usually buy AMD, it has been my experience that AMDs are not as reliable. Reliable enough, usually, but... I've had two fail, while I've never had an Intel chip fail. And before you think that's just because I use more AMD chips, that's actually not true - I usually buy AMDs brand new, but I've used a lot of Intels, gotten secondhand for free or cheap. So all things being equal you'd think the Intels would have failed more often for me.

      Oh well, anecdotal evidence of course, so not worth much... but Intel chips have had the capability to turn themselves off when they are in danger of heat damage, which last I heard AMD still won't do. For most purposes AMDs are still better value, but I think there's a reason to buy Intel sometimes as well.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
  18. Finally caught on? by freidog · · Score: 5, Insightful

    Chip Architect was speculating on this way back when intel's 64 bit extensions were still called Yamhill. They make some interesting observations that lead them to belive the second 32 bit ALU was to allow for 64 bit integer operations in a 2x32 bit format. And not to assist with eliminating resource shortages in HT as some others had suggested.
    And even if that does pan out it's highly unlikley to appear in desktop Prescott core chips anytime soon. Seems much more like something you'd find in Xeon MPs and later DPs to eliminate the need for that hack they call PAE.
    Though i hardly see how 'somebody told us a seinor exec said' makes Slashdot.' (I understand that's what the Inquirier bases most of their news on, i thought we had slightly higher standards of reliability)

    1. Re:Finally caught on? by drinkypoo · · Score: 1

      It makes sense that it would be a vector processing unit. It would take the wind out of Apple's sales a little - "Look, just like altivec!" When coupled with HT it would make it quite feasible to be able to handle 4x16 or 2x32 vectors with no software changes. As a bonus, it would reduce resource shortages in HT, though probably not eliminate them. Nothing is a second processor but a second processor, after all.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Finally caught on? by sessamoid · · Score: 1
      Though i hardly see how 'somebody told us a seinor exec said' makes Slashdot.' (I understand that's what the Inquirier bases most of their news on, i thought we had slightly higher standards of reliability)

      It's and old joke but it applies here, so I'll say it...

      "You're new around here, aren't you?"

      :)

      --
      "No, no, no. Don't tug on that. You never know what it might be attached to."
    3. Re:Finally caught on? by TheLink · · Score: 1

      Must be from an alternate universe or something.
      Doh.

      --
    4. Re:Finally caught on? by akuma(x86) · · Score: 1

      Though i hardly see how 'somebody told us a seinor exec said' makes Slashdot.' (I understand that's what the Inquirier bases most of their news on, i thought we had slightly higher standards of reliability)

      You're new here aren't you?

    5. Re:Finally caught on? by Natalie's+Hot+Grits · · Score: 1

      And HT was never designed nor marketed tward being a second processor. It's only reason for existance is because they wanted to fill their long pipeline with reasonably no effort. it worked, and so HT worked.

      Now they are just tweaking the concept to reduce bottleneks with reasonable cost in their next generation of HT.

      Afterall, if you really want dual CPU's, HT will never give you what you want. HT was never designed for CPU bound SMP applications. Never.

      --
      Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
  19. There's more to it than 64-bit instructions by StandardCell · · Score: 4, Interesting

    For one thing, I wonder what its physical external address bus looks like. Can it address more than 4GB of physical memory without paging? The Athlon64 and Opteron can. In addition, they are discounting the benefits of an on-board memory controller. This feature alone is a huge performance boost. To top it off, AMD gear comes with HyperTransport and a host of other goodies associated with AMD, like nForce chipsets with the best on-board sound of any integrated solution (and I don't suspect this will be different with nForce3 chipsets). In short, it seems like Intel is starting a concerted marketing blitz against AMD but with little avail. With the Prescott and this new extreme edition P4 with 2.5MB cache (I shudder at the yield hit that much cache has per wafer for them), we have a lot of sudden refocus towards Intel just prior to the launch. Product quality counts, but so does marketing.

    1. Re:There's more to it than 64-bit instructions by Wesley+Felter · · Score: 3, Informative

      Intel x86 CPUs can already address 36 bits of physical memory, which should be enough for the next few years.

      Intel doesn't do on-board memory controllers because they got burned by Timna.

    2. Re:There's more to it than 64-bit instructions by bofkentucky · · Score: 1

      when you have working 12"/300mm chip fabs and a (fairly) smooth transition to .13 and .09 micron dies, you can loose a few cores every now and then and not worry about it.

      --
      09f911029d74e35bd84156c5635688c0
    3. Re:There's more to it than 64-bit instructions by Andorion · · Score: 1

      FYI, the cache on the P4 Extreme is Level 2 - it's in the same package, but not on the same wafer as the logic. ~Berj

    4. Re:There's more to it than 64-bit instructions by Yoda's+Mum · · Score: 1

      Actually, it's 512kb level 2, like a standard Northwood Pentium 4, with an additional 2MB of level 3 cache.

      The effect of the extra cache should really help it against the A64's on-chip memory controller. Plus, it still allows the P4 to keep all the other advantages of a separate memory controller, such as being able to easily change the memory bus without CPU core changes. Where would the P4 be now if they originally designed it with an on-chip RAMBUS controller?

    5. Re:There's more to it than 64-bit instructions by Anonymous Coward · · Score: 0

      I thought the P4 did originally have an on-chip RAMBUS controller.

      Anyway, AMD faces the same problem. They support DDR266 onchip, but now the latest sexy thing is DDR500. Expect mobo companies to bypass the onchip controller and use their own.

    6. Re:There's more to it than 64-bit instructions by Anonymous Coward · · Score: 0

      Actually the oboard controller of the A64 supports PC3200, as this is the fastest official standard so far. If you overclock, it will work at PC4000 speeds as well.

      Skipping the internal controller would mean extra cost and less performance, not something you would want...

    7. Re:There's more to it than 64-bit instructions by Anonymous Coward · · Score: 0

      P4EE isn't produced on 90nm, and intel has clearly had a lot of problems with the 90nm process.

    8. Re:There's more to it than 64-bit instructions by Yoda's+Mum · · Score: 1

      Either way, it makes the chip far more inflexible than a CPU with a separate external memory controller. Anyway, as the preliminary P4 EE benchmarks seem to show, a large cache can effectively make up for an external memory controller.

      With DDR-II just around the corner, an on-chip memory controller's probably wasn't the smartest move for AMD. Either way, its going to be interesting to see how quickly/easily AMD are able to make use of new memory standards. My guess is that it's not going to be pretty.

    9. Re:There's more to it than 64-bit instructions by p3d0 · · Score: 1
      For one thing, I wonder what its physical external address bus looks like. Can it address more than 4GB of physical memory without paging?
      Paging has nothing to do with how much physical memory you can access. Paging is a way to get more virtual memory by caching a large, slow backing store (ie. disk) in physical memory.
      The Athlon64 and Opteron can.
      So can the Xeon. 32-bit chips can be designed to access any amount of physical ram. It's virtual memory that's typically limited to 32 bits.
      With the Prescott and this new extreme edition P4 with 2.5MB cache (I shudder at the yield hit that much cache has per wafer for them)...
      Not knowing anything about their fab techniques, I would suspect they would make the cache the way RAM is made: with redundant banks that can be disabled if they are flawed. This would substantially increase the yield despite the extra die area.
      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    10. Re:There's more to it than 64-bit instructions by Anonymous Coward · · Score: 0

      Any integration makes stuff less flexible, but it's usually worth it for performance and/or cost reasons.

      DDRII support will come at the 90nm shrink most likely.

      Also DDRII isn't all that great, really. Normal DDR is faster at the same clock frequency, so DDRII must clock far higher before it has any benefit. Normal DDR was never expected to clock this high...

    11. Re:There's more to it than 64-bit instructions by kasperd · · Score: 1

      Intel x86 CPUs can already address 36 bits of physical memory, which should be enough for the next few years.

      Correct, the problem is not the physical memory bits, but rather that they only have 32 bits of logical address space. The 32 bits of logical address space has been too small for a long time. If I cannot mmap my entire harddisk, I don't have enough address space. The trouble involved with 64 and 128 bits integer arithmetics is another reason we want architectures with more than 32 bits.

      --

      Do you care about the security of your wireless mouse?
    12. Re:There's more to it than 64-bit instructions by Anonymous Coward · · Score: 0

      Intel's 36 bit addressing (PAE) is a huge hack, and it still only supports 32 bit addressing in the programs.

      AMD's current technology (Opteron & Athlon64) supports 48 bit addressing, and when the time comes that 48 bits isn't enough, the change to full 64 bit addressing is not a difficult one (nothing like the current transition from 32 bits to more - the architecture already supports 64 bit addressing, it just hasn't been implemented in silicon yet because it isn't needed yet. Whereas x86-32 does NOT support anything over 32 bits, ever).

    13. Re:There's more to it than 64-bit instructions by Natalie's+Hot+Grits · · Score: 1

      One reason it is beneficial for AMD to have an on chip controller is that now they don't have to rely on 3rd parties (like VIA) to provide their performance... AMD isn't a chipset company. But they were forced to provide working north bridges for their Athlons because of crappy quality coming out of taiwan. Just look at the fact that the only stable chipsets available for the AMD platform used to be low performance AMD branded northbridges... Introduce nForce and the situation changed somewhat, but they arrived way after AMD64 was designed.

      But the overall idea is 2 things:

      1) higher performance memory interface (the new transmeta's do the same thing)
      2) no reliance on 3rd party chip makers to provide AMD's platform with a high performance and stable memory interface.

      Do you remember how unstable athlon systems were before nForce was out? I do. And it sucked. AMD's entire bad reputation of being unstable (including the K5 and K6-X product line) is directly caused by lack of quality in ALi,VIA, and SiS northbridges.

      Nobody is going to be bypassing AMD's memory controller. Look at the past.. When have you seen a new northbridge that supported faster memory than the CPU origionally did.. Well, i remember the 333-> 400MHz transition. And the 400MHz motherboards with a 333MHz cpu actually degraded performance because the FSB and memory bus were not synched. In fact, there has never been any platform where the FSB was different than the memory bus on an officially supported level since athlon came out.. So why would this be a problem? The P4 situation is the same way, they keep the FSB synched with the memory bus.

      When new memory technologys come out, you must BUY a new cpu to get that memory supported with any reasonable performance increase. This is true with the athlon64/Opteron, and it has ALWAYS been true for every CPU in the near past, including all Athlons,Durons,P3s, and P4s. The benefits of off die memory controllers has absolutely NOTHING to do with it being easier to support future memory technologies.

      --
      Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
    14. Re:There's more to it than 64-bit instructions by thisgooroo · · Score: 1
      the architecture already supports 64 bit addressing, it just hasn't been implemented in silicon yet because it isn't needed yet.

      huge mistake (unless software writers are careful), reminding me of the old IBM/360: they were 32 bit machines with a 24 bit address bus, and lots of software used the extra 8 bits in a word to encode extra information. turned out to be a huge nightmare when they wanted to extend to full 32 bit addressing

    15. Re:There's more to it than 64-bit instructions by Anonymous Coward · · Score: 0

      "Paging" can also mean the same thing as "segmentation". That is, having some upper bits of an address space controller by one register while the rest of the address comes from somewhere else. Consider, for an unusual example, the "zero-page" address space and instructions on 8-bit Motorola processors like the 6502 / 6809. Or look at the documentation for your MMU; odds are it refers to its "page table(s)".

    16. Re:There's more to it than 64-bit instructions by aminorex · · Score: 1

      > can already address 36 bits

      umm... you got a compiler that will support that?

      I didn't think so.

      It would be fun to see you write code that
      loops over 1G of 64-bit floating point numbers.

      No, I take that back -- I like you:P

      --
      -I like my women like I like my tea: green-
    17. Re:There's more to it than 64-bit instructions by Wesley+Felter · · Score: 1

      The correct solution to this is pretty simple: page-fault if the reserved bits are not zero. Of course, we just saw two examples of processors that didn't get this right, so let's hope that AMD did.

    18. Re:There's more to it than 64-bit instructions by Wesley+Felter · · Score: 1

      Hey aminorex.

      The compiler has nothing to do with PAE. In fact, only the kernel VM subsystem needs to deal with PAE, and it can piece together physical page numbers manually.

      I didn't say that userspace code can access 36 bits of memory. All I meant is that the P7 bus protocol supports 36 bits of physical memory and thus doesn't need to change in the near future. Obviously a CPU with 64-bit virtual and 36-bit physical addresses is preferable to the current situation of 32-bit virtual and 36-bit physical.

    19. Re:There's more to it than 64-bit instructions by aminorex · · Score: 1

      Actually, userspace code can access 36 bits of
      memory. It just has to span multiple protection
      domains in order to do it.

      I once worked on a compiler that could be used to
      generate code to do this. It was a multi-million
      $ project, although with current tech, I'm sure
      I could approximate it fairly well for under
      $100K.

      36 bits is a measly 64GB. That's about $10K
      these days. I think it needed to change a few
      years ago.

      What would *you* do if you could directly
      address a terabyte or two of RAM?
      Post-stack migration? QCD? MBR time-sequence
      prediction? This stuff that used to take
      supercomputers becomes feasible on COTS
      hardware.

      --
      -I like my women like I like my tea: green-
    20. Re:There's more to it than 64-bit instructions by Guy+Harris · · Score: 1
      Actually, userspace code can access 36 bits of memory. It just has to span multiple protection domains in order to do it.

      ...or use mmap(). (I'd say "...mmap() or MapViewOfFile(), but I'm not sure any version of Windows treats memory above 4GB the same way it treats the first 4GB. There might be non-UNIXy OSes that support it as well, so maybe there are other APIs that can be used.)

    21. Re:There's more to it than 64-bit instructions by Ninja+Programmer · · Score: 1

      To address those extra 4 bits you need to rearchitect the OS, the compiler, and your application (remember far pointers everyone?) All just to get a measely few more years of life out of 32-bit x86. Sorry, but that's a non-solution.

    22. Re:There's more to it than 64-bit instructions by Wesley+Felter · · Score: 1

      Another person not getting my point.

      DO NOT EVEN TRY to use more than 4GB of memory in a single app on a 32-bit processor. That is not what PAE is for.

  20. Re:gotta compete by Anonymous Coward · · Score: 3, Insightful

    You're reasoning is faulty. In fact, it is the presence of competition and the inability of Intel to completely shape the PC platform that is holding back technology.

    Look at the Apple Macintosh. The platform is completely proprietary, and controlled by Apple. Apple successfully switched architectures in the mid-90s, from the CISC 68000 to the PowerPC. These architectures were completely incompatible at the machine code level. But since no one was selling souped-up knockoff 68000 Mac clones in competition, the PowerPC was the only way forward and all users eventually upgraded. Apple is going to do the same thing again, this time to the 64-bit platform, and no one is dragging their feet this time either.

    This happens all the time when hardware is proprietary. Sun, HP, and SGI all used to sell workstations based on the 68000 architecture, and were able to transition to RISC architectures due to the proprietary platform. But look at the PC architecture...the same outdated CISC architecture that was used in 1981 is still there in today's PC's. If Intel had complete control, we'd all have switched to the i960 or Itanium by now. But no, there is competition, so we're stuck in the past.

  21. Re:gotta compete by Anonymous Coward · · Score: 0

    The whole reason this is interesting is because most people originally thought 64 bit functionality was where the 2 main chipmakers would differ. AMD were offering a hybrid, whereas intel seemed to be going straight to full 64 bit. Now it seems like they're possibly offering a hybrid as well. Its not about pure competition, its about which way 64 chips are going to go.

  22. Deputy prime minister by sonoluminescence · · Score: 1

    Wow! Prescott two jabs, two jags and now 64 bit. Vote Labour powered by a 64 bit Deputy prime minister. http://politics.guardian.co.uk/person/0,,-4254.htm l (sorry UK specific)

    --
    Karma: Bad. Calmer, good.
    1. Re:Deputy prime minister by eyeye · · Score: 1

      I always think of the fat grumpy bugger when I hear prescott too :)

      --
      Bush and Blair ate my sig!
    2. Re:Deputy prime minister by TomV · · Score: 1

      And it has to be said, that punch was the single most honest response by any politician I have ever seen or ever expect to see in my life. SUCH a refreshing change.

  23. Performance doesn't come directly from 64 bits by vlad_petric · · Score: 4, Informative
    MMX and SSE can already do integer operations on 64 bits ... What people don't realize is that the performance improvement comes from a significant change in the instruction set architecture (ISA). While x86 is the most commercially-successful ISA, it is ugly as hell, difficult to compile for and stressing the memory system unnecessarily, as it has very few registers ("difficult to explain and impossible to love" once said an Intel designer).

    Itanium is a full fix to the problem. The horrendous x86 ISA is completely replaced by an explicitly-parallel (EPIC) instruction set that has all the nice properties of a RISC machine (easier to compile for, less stress on the memory system as you get 128 registers, easier for the machine to decode the instructions as they're fix format and don't require RISC conversion, etc.). The problems with it are:

    1. You need a compiler that "knows" how to bundle instructions effectively (a VLIW-compiler). GCC clearly isn't there yet (it's not uncommon for the intel compiler to beat gcc by 30->50% when running computationally-intensive stuff)

    2. Being completely different than x86, it can't be very efficient at emulating x86 programs.

    AMD partially fixes the problem by extending the x86 ISA to 64 bits, *and* adding 8 general purpose registers. Because they just extended the ISA, running old code is just as fast. Furthermore, new code can benefit from from the extra 8 registers, and run even faster.

    For the short term the Opteron is a pretty impressive chip, but I really don't see how AMD is going to stay on Moore's curve with such a shitty instruction set architecture.

    P.S. Clearly 32 bits can only address 4GB of RAM, and for *some* servers more addressing space buys you something. But I'd say they are a very small minority.

    --

    The Raven

    1. Re:Performance doesn't come directly from 64 bits by Unregistered · · Score: 1

      you forget: x86 works. There are already of compilers used to x86. I have no idea why amd didn't add more registeres, but otherwise their move makes as much sense as intel's.

    2. Re:Performance doesn't come directly from 64 bits by khuber · · Score: 2, Informative
      P.S. Clearly 32 bits can only address 4GB of RAM

      Intel has had more than 32 bit addressing since the Pentium Pro, which introduced 36 bit physical addresses (64 GB).

    3. Re:Performance doesn't come directly from 64 bits by Marrow · · Score: 1

      P.S. Clearly 32 bits can only address 4GB of RAM

      at one time....

      In a segmented memory architecture, you can address a lot more than that. Not that I love segment registers. Just being picky.

    4. Re:Performance doesn't come directly from 64 bits by vlad_petric · · Score: 2, Informative

      Yeah, but support for in the 2 major x86 OSes (Win & Linux) is rather flaky. Furthermore, a "normal" app is still limited to 4G by the OS.

      --

      The Raven

    5. Re:Performance doesn't come directly from 64 bits by ScrewMaster · · Score: 1

      The real question is how many times the computer industry can recycle the acronym "ISA".

      --
      The higher the technology, the sharper that two-edged sword.
    6. Re:Performance doesn't come directly from 64 bits by addaon · · Score: 2, Funny

      I Suspect Another Is Somewhat Appropriate...

      --

      I've had this sig for three days.
    7. Re:Performance doesn't come directly from 64 bits by stu72 · · Score: 1

      Funny on this - I was in a Mac store the other day, drooling over the G5. I love the G5 design but I could never afford it, no matter how slick. Nevertheless, when the sales droid came over I let him give me the speil and I was astounded - he was explaining how 64 bits was better because you could load all your programs into memory and not use the hard drive anymore. I was totally blown away.

    8. Re:Performance doesn't come directly from 64 bits by drinkypoo · · Score: 4, Informative
      AMD did add more registers. In fact, they quadrupled the number of registers. Vlad asserts that x86 has eight GPRs, and that x86-64 just adds eight more, but he is wrong on both counts. x86 has four GPRs, [E]AX through [E]DX (The "E" means 32 bit) and it has four index registers - actually two index registers, and two index offset registers - which can be used with some instructions. Many x86 instructions specify that your result must be stored in a specific register or pair of registers (for 64 bit results of multiply operations for example) and none of those results go into the address index registers. Furthermore, many instructions require that you use the index registers for - gasp - addressing, and they look at those registers to determine where to get information, and/or where to store it. Hence, you have FOUR general purpose registers in x86. If you want to be really strict about it, you have zero general purpose registers on the x86, because each of the four so-called GPRs has a purpose to many instructions. CX, for example, must be used for your counter by many instructions, so when writing assembler you are forever having to take into account where each instruction is going to want to look for data. Modern x86-compatible processors actually have a whole shitload of temporary registers and do register renaming so that when you think you're moving data from register to register to avoid this problem, the CPU is actually leaving it in place and just renaming the registers. This is true of the processors from both Intel and AMD, and presumably even the VIA processors, though I have no information there.

      Now, I admit I haven't spent a lot of time looking through my x86-64 manuals, because it's been vaporware until fairly recently, and furthermore they lied to us about how many HT buses would be on each flavor of processor right up until the very end, so I won't be buying anything until either they bring out an Athlon 64 MP which has the missing hypertransport bus re-added, or until the Athlon 64 brings down the price of Opteron processors. My Athlon XP is holding me for the time being, and besides, there's no 64 bit windows yet. Even after there IS a 64 bit windows, I expect to have to wait a little while for some of my drivers. So it hasn't really been a serious consideration for me. But I suspect that in many cases they have provided us with new instructions to replace the old instructions which require that the result go into specific registers.

      So, x86-64 has 16 GPRs, plus 16 "XMM" registers for SSE/SSE2, not to mention it implements the SSE2 functions from the P4. I think it pretty effectively does all the things it needs to do. Meanwhile it still has hardware solutions for emulating all the deficiencies of the x86 so that it can maintain backwards compatibility without sloowowwwwwing dooowowwwnnnn like itanic. It's the perfect solution for those persons who are not ready to give up their backwards compatibility, and it does not have the flaws that you and vlad assert. If you don't believe me, go root around AMD's site for the PDFs. Hell, I even got them to send me the paper documentation for free, which I intended to read in the bathroom. Unfortunately, even my wholly irrelevant nintendo summer 2003 catalog has been water damaged in there, so I'm definitely not going to venture into the latrine with my AMD technical docs.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:Performance doesn't come directly from 64 bits by drinkypoo · · Score: 1

      Four gigs, minus the amount of shared memory, but that's still more than four gigs, minus all the allocated memory of everything else on the system. There is still a definite advantage there. Of course, it will affect most of us not at all.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    10. Re:Performance doesn't come directly from 64 bits by Unregistered · · Score: 1

      I know a little assembly and realized that 12 more registers is a huge improvement, but i was under the impression that RISC chips and such had way more than 16 registers.

    11. Re:Performance doesn't come directly from 64 bits by drinkypoo · · Score: 1

      Some of them do have more than 16 registers. I recall someone at AMD saying that they would have liked to have more registers but that their current design didn't really allow for it. I suspect that they'll add more registers in a later version. That's probably a long, long way off though.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    12. Re:Performance doesn't come directly from 64 bits by scheme · · Score: 5, Informative
      Itanium is a full fix to the problem. The horrendous x86 ISA is completely replaced by an explicitly-parallel (EPIC) instruction set that has all the nice properties of a RISC machine (easier to compile for, less stress on the memory system as you get 128 registers, easier for the machine to decode the instructions as they're fix format and don't require RISC conversion, etc.). The problems with it are:
      1. You need a compiler that "knows" how to bundle instructions effectively (a VLIW-compiler). GCC clearly isn't there yet (it's not uncommon for the intel compiler to beat gcc by 30->50% when running computationally-intensive stuff)
      2. Being completely different than x86, it can't be very efficient at emulating x86 programs.

      The Itanium ISA is elegant an and clean in some places but in others is an ungodly mess of complicated things. Take the register save engine (RSE) for example. It's supposed to handle spilling registers to the stack and loading them to the stack. This includes handling page faults, exceptions, interrupts, and memory errors. Oh yeah, this is supposed to be automatic and handled invisibly by hardware without software intervention. Hasn't happened yet.

      Also the EPIC ISA that the Itanium uses isn't easy to compile for. This is one of the biggest problems with the Itanium. It requires compilers to pull out a lot of parallelism in the code and present that to the hardware for execution. Intel sort of glossed over this when introducing the Itanium about 10 years ago and the compiler technology hasn't been able to really do this. So although the Intel compiler is better than gcc, it still isn't all that great.

      Incidentally, the Itanium does a better job at emulating the x86 ISA in software than in hardware. It was a big deal a few months ago when Intel introduced a software x86 emulator that offered a dramatic improvement over using the built in hardware emulation.

      --
      "When you sit with a nice girl for two hours, it seems like two minutes. When you sit on a hot stove for two minutes, it
    13. Re:Performance doesn't come directly from 64 bits by William+Baric · · Score: 1

      I really don't see how AMD is going to stay on Moore's curve with such a shitty instruction set architecture

      I'm not an expert in processor architecture but I believe every x86 processor since the pentium (pro?) has a RISC core.

    14. Re:Performance doesn't come directly from 64 bits by vlad_petric · · Score: 1

      The problem is not CISC vs. RISC. You do lose a little bit by having to convert CISC to RISC, but that's manageable. The problem is the number of registers. The compiler can barely allocate 2->3 registers to variables, and consequently has to go to memory many more times than a RISC processor (which usually has 32->128 registers). Accessing registers is much faster than going to memory, even if you hit in the first level cache (and if you don't hit in the caches and have to go all the way to the DRAMs, you'll wait about ~100->400 cycles ...)

      --

      The Raven

    15. Re:Performance doesn't come directly from 64 bits by Anonymous Coward · · Score: 0

      P.S. Clearly 32 bits can only address 4GB of RAM, and for *some* servers more addressing space buys you something.

      P.P.S. Don't forget memory paging and segmentation. Modern intel processors support this for addressing far more than 4GB of physical RAM (don't forget it already does this for addressing virtual memory!)

    16. Re:Performance doesn't come directly from 64 bits by hoof · · Score: 1
      X86 certainly is ugly as hell. But IMHO, it looks very clean next to Itanium/IA64.

      The problem with Itanium/IA64 is that it has just about every feature that has ever been proposed for an ISA bundled together in one giant mess, with the big feature being that it is EPIC - explicitly parallel. This means that if you have an instruction that depends on the result of a previous instruction, it must be separated from that instruction with a 'stop'. As a result, the instruction groups between the stops can be executed in parallel without any messy dependency checking that a normal architecture requires to run instructions out of order.

      It sounds reasonable, but the catch is that to get good performance, you need more parallelism than is encoded in the explicitly parallel instruction groups. Newer IA64 implementations will run instruction groups out of order and have to do dependency checking between them, just like a regular x86. So now you are stuck with a complicated explicitly parallel instruction encoding and a processor that still needs to check dependencies at run time. The goofy encoding gets you nothing.

      All this, yet they couldn't find room for a reg+offset addressing mode.

      On the other hand, AMD has just taken the x86 and removed all the major problems. An x86 with more registers and a non stack based FPU is actually a pretty nice ISA.

    17. Re:Performance doesn't come directly from 64 bits by Anonymous Coward · · Score: 0

      MMX and SSE can already do integer operations on 64 bits

      No they don't perform 64bit operations, they may operate on 64bit registers but they only do at most 32 bit operations. it is used to perform one instruction on a set of data (called SIMD, single instruction, multiple data). so they perform a certain operation on two/four/eight distinct 32/16/8 bit data values. A single MMX/SSE instruction can not manipulate a 64bit data value like adding, subtraction, shifting... etc two (one in the case of shifting) 64bit values. The Athlon 64 has instuctions that work on 64bit data directly.

    18. Re:Performance doesn't come directly from 64 bits by William+Baric · · Score: 1

      Hmmm... I think you're preaching to a converted here! The first processor I learned was the 6502 (well, at least it was the first I really used); then I learned the 68000 and I was impressed by how powerful it was; then, because of all the hype, I decided to learn the 386, expecting to see the same kind of improvement I saw going from the 6502 to the 68000...
      At first I was shocked by the 386 (what the fuck is this piece of shit)...
      Then it was denial (it's not possible : I must have the wrong book)...
      Then it was bargainning (if I read the book 2 or 3 more times I will get it and realize how good a 386 is)...
      Then it was fear (I DON'T GET IT!!!)...
      After was anger (I hate all those fucking morons who think a 386 is a great piece of hardware)...
      Then despair (computer science is not for me)...
      And finally Acceptance (people are stupid, I'm the only intelligent being on earth and I'll simply forget about assembly).

    19. Re:Performance doesn't come directly from 64 bits by Anonymous Coward · · Score: 0

      You have to understand that changing the ISA is disasterous for both intel and AMD. the reason the ISA sucks is because they wanted to maintain backwards compatibility. other chips which ignore backword compatibility have better ISAs. why does intel support backwards compatibility you probably wondering? Well they really don't have much of a choice. programmers will not want do convert their programs to use a new ISA. Intel learned this important lesson long ago when they were trying to release the secessor of the 8088 (or was that the 8086) chip. maybe now it would be different but i doubt it. I totally agree that the ISA needs to be changed but changing it could mean that people will not use the new ISA. and especially right now when Intel and AMD are almost neck to neck, the company that changes the ISA will be commiting suicide.

    20. Re:Performance doesn't come directly from 64 bits by p3d0 · · Score: 1
      For the short term the Opteron is a pretty impressive chip, but I really don't see how AMD is going to stay on Moore's curve with such a shitty instruction set architecture.
      The P4's trace cache has made the ISA largely irrelevant. P4s translate x86 instructions into something more RISC-like internally and then never touch x86 instructions again. It's basically Crusoe in hardware.

      With this scheme, x86 is actually a pretty good ISA, because with a trace cache, the only thing about the ISA that matters is code density, and x86's code density is quite good.

      Remember, no prediction fails more consistently than one that claims CPUs will not maintain Moore's law.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    21. Re:Performance doesn't come directly from 64 bits by p3d0 · · Score: 1
      Clearly 32 bits can only address 4GB of RAM, and for *some* servers more addressing space buys you something. But I'd say they are a very small minority.
      Wow, that's an astoundingly ignorant and arrogant statement. I don't even know where to begin.
      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    22. Re:Performance doesn't come directly from 64 bits by p3d0 · · Score: 1
      x86 has four GPRs, [E]AX through [E]DX (The "E" means 32 bit) and it has four index registers - actually two index registers, and two index offset registers - which can be used with some instructions. Many x86 instructions specify that your result must be stored in a specific register or pair of registers (for 64 bit results of multiply operations for example) and none of those results go into the address index registers.
      No, that doesn't matter in practice. The most commonly used integer operations (mov, addition, dereferencing) work with any of the 8 registers. Many instructions that need special registers are so long-running (eg. rep mov) that the extra time to shuffle things into the right registers is negligible.

      Finally, consider the worst-case scenario: you really do have 7 numbers that need to be involved in, say, shifting, so they all need to be in ECX at various times. So you need to insert a number of movs or xchgs to shuffle the data around in preparation for each shift. It's still better than spilling to RAM, which you would need to do if you only had 4 registers. Furthermore, inside the P4's trace cache, though I don't know the details, surely all moves get optimized away and the actual code that runs behaves as though it has lots of registers.

      In short, x86 performs as though it has 8 GPRs (including the stack pointer), not 4.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    23. Re:Performance doesn't come directly from 64 bits by Anonymous Coward · · Score: 0

      Having more than 4GB of _address space_ is useful more often than you might think. Many applications assume that address space is cheap and plentiful and that physical memory isn't. That was a good assumption until recently but nowadays, even cheap servers have almost as much physical memory as a process has address space. For example, a worker process running ASP.NET on IIS6 can only grow to 800MB before it risks hitting OutOfMemoryException due to lack of address space. And the CLR is fairly new code written by smart people. It's bound to be worse for many other applications. I'm not buying expensive servers and I'm running fairly mainstream applications but I'm still in a situation where there's no point adding physical RAM because apps hit the address space ceiling first. I'm looking forward to cheap and ubiquitous 64 bit.

      Experience of the last few years has shown that instruction set isn't as important a factor in processor design as it was once believed. A few years ago, everybody believed, as you do, that x86's problems were insurmountable. But then they solved them:
      * Of of order execution enables parallelism.
      * Register renaming relieves register stress.
      * Improvements to the memory interface practically eliminate the cost of the redundant load/stores caused by having so few registers (they don't really go to/from memory).
      * Cracking x86 instructions to RISC-style eliminates most x86 decode/complexity problems such as variable instruction length.
      * Even the cost of the evil FPU stack is largely eliminated in PIII and K7/8.

      Furthermore, the Itanium architecture isn't as great as it sounds. It's not clear that any of Itanium's performance is due to IA64 - most observers attribute its good performance to other factors such as its memory interface/cache.

    24. Re:Performance doesn't come directly from 64 bits by kasperd · · Score: 1

      In a segmented memory architecture, you can address a lot more than that.

      That might be true for some architectures. But the way Intel designed 386 protected mode and later PAE, you are still limited to 4GB even with segmentation. And typically 1GB of that is reserved for the kernel.

      --

      Do you care about the security of your wireless mouse?
    25. Re:Performance doesn't come directly from 64 bits by TomV · · Score: 1

      It's Swiftly Approaching
      Industry Standard Acronym
      In Several Areas

    26. Re:Performance doesn't come directly from 64 bits by kasperd · · Score: 1

      people are stupid,
      Yes.

      I'm the only intelligent being on earth
      No, but we are part of a minority.

      and I'll simply forget about assembly
      Good choice.

      --

      Do you care about the security of your wireless mouse?
    27. Re:Performance doesn't come directly from 64 bits by Anonymous Coward · · Score: 0

      I was totally blown away.

      It's disgusting what Apple reps will do to make a sale.

    28. Re:Performance doesn't come directly from 64 bits by thisgooroo · · Score: 1

      hardly possible: the number of registers has a big effect on instruction formats. if they add more not hidden registers, they have to completely redesign the instruction set

    29. Re:Performance doesn't come directly from 64 bits by thisgooroo · · Score: 1

      you must live in a dreamworld if you think that only apple reps do that. this is as old as the computer industry (actually: since sales people exist)

    30. Re:Performance doesn't come directly from 64 bits by thisgooroo · · Score: 1

      the only reason why backward compatibility is needed is because many programs are released in binary only. with source distribution it would not be necessary: in most cases a recompilation would sufffice (ok, some things need adjustment)

    31. Re:Performance doesn't come directly from 64 bits by yerricde · · Score: 1

      i was under the impression that RISC chips and such had way more than 16 registers.

      Not all RISC architectures are register-heavy; the ARM architecture has 15 general-purpose registers. Remember that more registers means either 1. the instruction word grows longer, or 2. some features must be forfeited.

      --
      Will I retire or break 10K?
    32. Re:Performance doesn't come directly from 64 bits by drinkypoo · · Score: 1

      Not if they designed the instruction set with more registers in mind from the beginning. I don't know if they did, and I'm not looking at the documentation right now, because I just got back from a wedding and I'm buzzed on mudslides. And tomorrow, I have to strip a bunch of paint off a truck.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    33. Re:Performance doesn't come directly from 64 bits by thisgooroo · · Score: 1

      they didn't

  24. You must be rich. by Futurepower(R) · · Score: 1

    I don't know why you need 64,000 of something. I have only one abacus.

    1. Re:You must be rich. by Anonymous Coward · · Score: 0

      And what's even worse, is that you probably think that is funny.

  25. Re:BAH! 286 is all you need. by Guppy06 · · Score: 1

    You know, some of us actually like to use a processor that multitasks. You should have said that a 386 is all you need, so you can (kinda) run vi and emacs on linux and properly participate in the editor wars.

  26. You know you're in trouble... by Anonymous Coward · · Score: 2, Funny

    ...when your 100w processor comes with heat sink and a complementary jiffy pop.

  27. FUD! by Tremblay99 · · Score: 5, Insightful

    Fear, uncertainty, doubt ... not just the tool of Microsoft! Let's see ... the Athlon 64 is out, officially, in a few days ... Intel's 64 bit part, the Itanium, is having trouble shaking its nickname, Itanic ... lots of developers are excited 'bout having a chip running 64 and 32 bit software. Solution? Don't make a better chip ... just float a rumour that you'll be producing something better with some 64 bit instructions... Real Soon Now! With luck, you'll tank the sales of your competitor's chip, without doing any real work! Blah blah blah.

    1. Re:FUD! by JayBlalock · · Score: 4, Insightful

      Someone with points mod this up. If Intel ACTUALLY had a 64-bitter coming out soon, they'd be trumpeting it like it was the Second Coming. With AMD's new chip about to hit, it would be the only sensible thing to do, even if it's months off. There's no reason they would sit on it (and let just-above-tabloid tech sites "break" the story) *unless* they didn't actually have a competing product envisioned anytime soon.

      --
      Bush: He's Liberal in all the wrong ways.
    2. Re:FUD! by yomegaman · · Score: 1

      Intel has a better chip, they don't need FUD. Do a little research over at www.specbench.org and you'll see that the Itanium2 is blowing away anything else out there.

      --
      ...wearing a skin-tight topless leather jumpsuit, with cutaway buttocks and transparent crotch panel.
    3. Re:FUD! by hbo · · Score: 1

      If Intel ACTUALLY had a 64-bitter coming out soon, they'd be trumpeting it like it was the Second Coming.

      There's that multi-billion dollar investment in Itanium to think about not to mention the partneships Intel has tried to build around the chip.

      This is all about the server market. Itanium is expensive because it requires all new software. It's performance has been disappointing too. That has recently improved, they actually beat Opteron in the tests I've seen on 64-bit code. But Opteron's value proposition is that it runs current 32-bit apps and new 64 bit ones at the same time. So you can spread out that 6-9 figure investment in new software over a longer period than just a few quarters.

      What Intel really needs to do is to add ia32 compatibility to ia64 in the silicon. Then they could run the old cruft at speeds competitive with Opteron, while still offering a path forward out of the horrid architecture they, and the market, have tortured the world with for 20 years

      --

      "Even if you are on the right track, you'll get run over if you just sit there" - Will Rogers

    4. Re:FUD! by DarkEdgeX · · Score: 1

      Right.. like a General going into battle that's a little short on troops, but has some killer special forces that will hopefully, with surprise, defeat your foes, Intel should just blow their chances away by "trumpeting" their approach and giving away any and all measure of surprise.

      I'm not going to debate whether or not Prescott has 64-bit extensions, but assuming it does, and knowing that AMD thinks they have a sure thing, would YOU galavant about like a some idiot who arrived late at a party saying "look at me, look at me, I do 64-bit too!" or would you bide your time, then make the major announcement long after your opponents "shiny new thing(TM)" has had a chance to lose it's luster?

      I would.

      If Intel thinks they have something that will surprise people, there's NO sense making a big deal out of it and helping PUSH AMD's sales.

      --
      All I know about Bush is I had a good job when Clinton was president.
    5. Re:FUD! by JayBlalock · · Score: 1

      How exactly do you figure Intel announcing a home 23/64 chip would PUSH AMD's sales? AMD is still widely seen as the 2nd stringer in the processor arena. Processors aren't like jewelry. People don't buy whole new systems just because something has gone out of style. If Intel DID have a processor coming out in, say, four months, and didn't say a word, everyone who wanted a 32/64-bit proc would have already bought one. However, in the tech world, customers who've waited a long time for a product are almost always willing to wait a little longer. So you distract them with FUD of how your Extra Special Super Shiny chip is gonna blow AMD's out of the water, if only they wait another couple months. Just look at Apple buying figures - I don't have the specifics, but a LOT of people wait until after their major conventions to buy new stuff specifically so they know whether or not something new and shiny will be coming up a little later. So, again, we're back to "the chip is vapor, they're just trying to keep a few people from going AMD in the meantime."

      --
      Bush: He's Liberal in all the wrong ways.
    6. Re:FUD! by Anonymous Coward · · Score: 0

      Go price out a Itanium2 CPU and a Opteron CPU, now ask yourself, "is the better performance of the Itanium2 worth the vastly higher price?" If you're doing HPC maybe it is but the vast number of 64bit CPUs get assigned to fairly mundane server duties like running a database and if your company is anything like most of the companies out there then you have a tight budget and justifying double the expendature or more for just a few more transactions per second is going to be a very hard sell.

    7. Re:FUD! by yomegaman · · Score: 1

      Intel is charging a premium for the Itanium2 now because the people who need it REALLY need it and have the money to spend. If the AMD chips start making inroads I'm sure Intel will lower prices on the lower-end Itaniums, just like they always have with the Pentium lines.

      --
      ...wearing a skin-tight topless leather jumpsuit, with cutaway buttocks and transparent crotch panel.
    8. Re:FUD! by Anonymous Coward · · Score: 0

      Itanium is IA32 compatible "in the silicon". Intel went to great effort to makes sure it runs everything from CP/M-86 on up natively.

      Problem is it's very slow. In fact, for the price point of Itanium systems, it would have made much more sense just to bolt a seperate P4 CPU in there.

      In fact, you can argue that on a server system there's no need for x86 compatiblity at all. (Maybe to run WinZip...) Your software stack is going to be pretty limited and controlled.

      The reason that AMD is getting the hype is that Hammer is a credible desktop/workstation system. They don't really have any significiant advantage in the server market.

    9. Re:FUD! by Anonymous Coward · · Score: 0

      Keep in mind that Sun Sparc is the slowest chip availble in the midrange segement, yet Sun is #1 in sales.

      Lesson to be learned: There's a lot more to success than raw price/performance. The mere fact that one can buy an Itanium from IBM/HP/Dell and one can't buy a Opteron gives Intel a distinct leg up for corporate customers.

    10. Re:FUD! by paitre · · Score: 1

      And? It's still at an absolutely unaffordable price point.
      If Intel can provide me the highest end I2 in a dualy config with 4G of RAM (like I can get from Penguin) for under 4300 per system (TOTAL), you might have a point.

      I've got a budget, and I need to get the best bang for my buck out of it. Guess what -doesn't-? I2.
      Hands down.

    11. Re:FUD! by DarkEdgeX · · Score: 1
      How exactly do you figure Intel announcing a home 23/64 chip would PUSH AMD's sales?
      Because the Prescott CPU's won't be available at the same time as AMD's x86-64-based CPU's. Prescott will come a few months later-- meanwhile, an announcement from Intel of planned 64-bit extensions (whether or not compatible with x86-64) would simply fuel sales of AMD x86-64 CPU's.

      Of course it's all a matter of opinion as to how the market would react to an announcement from Intel of 64-bit extensions to the existing x86 ISA being included with Prescott, but I believe it would give AMD fuel to market x86-64, using the "we were first to deliver it, and the pioneers to push forward with it" argument.

      So, again, we're back to "the chip is vapor, they're just trying to keep a few people from going AMD in the meantime."
      As I said in my original reply, this is irrelevant and I will not debate it. I said, quite clearly, that I'll debate the issue from the assumption that they do indeed have 64-bit extensions in Prescott, and that they're production usable. I could honestly care less either way, because I don't buy AMD (and x86-64 isn't going to sway me in the slightest because Itanium already runs circles around it, and Itanium has been here for years).
      --
      All I know about Bush is I had a good job when Clinton was president.
    12. Re:FUD! by yomegaman · · Score: 1

      I do have a point, the Itanium2 has superior performance. I hope AMD's new chips are successful, that will force Intel to lower prices and that's good for all of us.

      --
      ...wearing a skin-tight topless leather jumpsuit, with cutaway buttocks and transparent crotch panel.
    13. Re:FUD! by hamster+foo · · Score: 1

      Ok, we'll work on the assumption that the Prescott has 64 bit instructions.

      That gives us two scenerioes.

      1. Intel doesn't make any press release saying it does, and AMD's chip launches. Verifying that AMD was the first to deliver.

      2. Intel makes a press release saying their yet to be released processor will have 64 bit extensions, and AMD's chip launches. Verifying that AMD was the first to deliver.

      Your logic seems flawed. How does a press release alter the public perception that AMD was the first to deliver if they will be the first to deliver regardless of any announcements?

      --
      - b
    14. Re:FUD! by DarkEdgeX · · Score: 1
      1. Intel doesn't make any press release saying it does, and AMD's chip launches. Verifying that AMD was the first to deliver.
      This is the scenario I believe will be played out if indeed Prescott even has 64-bit extensions and this isn't some story that really IS FUD mongering. It could very well be, afterall.

      Intel has no reason to trumpet their technology, as with 3D Now!, Intel can (and probably will) make a comeback and make people say "3D What!?". SSE has mostly stolen whatever thunder AMD had, and as with that, Intel will likely steal the thunder from x86-64 if Intel believes it to be viable and worth pursuit.

      Your logic seems flawed.
      Based on the history of prior technological revolutions that AMD has pioneered, my logic is in fact far from flawed.

      It makes perfect sense that Intel would bide their time and announce product as it becomes available, not months in advance to appear as someone coming late to a party (and if they announced it now, they'd be late to the party, without anything to show anyone). They'll wait until their first Prescott CPU's ship, or just before, to announce anything I predict. And this'll happen pretty soon since the road maps show a Prescott CPU shipping in November.
      --
      All I know about Bush is I had a good job when Clinton was president.
    15. Re:FUD! by hamster+foo · · Score: 1

      "Of course it's all a matter of opinion as to how the market would react to an announcement from Intel of 64-bit extensions to the existing x86 ISA being included with Prescott, but I believe it would give AMD fuel to market x86-64, using the "we were first to deliver it, and the pioneers to push forward with it" argument."

      I'm not arguing any inference you made based on history. I'm arguing the logic in the above statement is flawed. The above makes no sense. Whether Intel makes an announcement or not, AMD WILL be able to say "we were first to deliver it, and the pioneers to push forward with it". They're going to be first to the market with it. That's a fact. Nothing Intel does can change that.

      Are you perhaps trying to say Intel marketing Prescott's 64 bit capability would make consumers not previously interested/aware of 64 bit computing interested/aware of it, and in doing so, provide fire for AMD sales of their already launched 64 bit offering? If that's the case, then I can see some logic there, but your intent was not very clear in that statement.

      The historical inferences I'm not arguing and was not commenting on.

      --
      - b
    16. Re:FUD! by Anonymous Coward · · Score: 0

      How exactly do you figure Intel announcing a home 23/64 chip would PUSH AMD's sales?

      Because I think few people would be interested in a 23-bit CPU. ;-)

    17. Re:FUD! by Tony+Hoyle · · Score: 1

      Even if itanic is better (and that's arguable, at this point) it won't do as well. We're back to VHSvsBeta again. Beta was a better technology, was first to market indeed... it failed. Simply because it had 1 hour tapes and VHS had 2 hour ones. [yes I know they both got 3 hour later but that was much later]

      The product that wins the battle is the one that has the features the consumer wants, at the price they want. At the moment athlon64 wipes the floor with itanium on price, backward compatibility, availablility of motherboards, etc. AMD have done the right thing - given copies to the benchmarkers and let them test games on it, where it trounces the P4 in 32bit mode. 64bit will be a selling point in a year or two - for now they're pushing the fact that these things are about the fastest out there.

    18. Re:FUD! by bhtooefr · · Score: 1

      Ah, but if the people wanted to fight for (buy from) the side that had killer special forces (a 64-bit x86), it would really help the general (Intel) to get someone to leak that they might have killer special forces (a 64-bit x86), because people might hesitate to join the other general (AMD).

    19. Re:FUD! by DarkEdgeX · · Score: 1
      Are you perhaps trying to say Intel marketing Prescott's 64 bit capability would make consumers not previously interested/aware of 64 bit computing interested/aware of it, and in doing so, provide fire for AMD sales of their already launched 64 bit offering? If that's the case, then I can see some logic there, but your intent was not very clear in that statement.
      Heh, this is what I thought I was saying all along. ;) Yes, this is what I meant-- Intel coming out and saying they have 64-bit extensions in Prescott would validate AMD's x86-64, essentially helping to drive sales of x86-64 based CPU's.
      --
      All I know about Bush is I had a good job when Clinton was president.
    20. Re:FUD! by Bedouin+X · · Score: 1

      Nothing except for the ridiculous scalability of the memory subsystem that increases almost exponentially with each CPU added. The Itanium FPU is a certifiable 8-headed fire-breathing monster, but there are a number of benchmarks where the Opterons hang tight at a fraction of the cost.

      --
      Dissolve... Resolve... Evolve...
    21. Re:FUD! by yomegaman · · Score: 1

      You may be right, but I don't envision the AMD chips "trouncing" the P4 in 32-bit mode. The Opterons don't seem to be doing it, so why would the Athlon64? Really, I think most of these predictions are nothing more than wishful thinking.

      --
      ...wearing a skin-tight topless leather jumpsuit, with cutaway buttocks and transparent crotch panel.
    22. Re:FUD! by Bedouin+X · · Score: 1

      Well you CAN buy one from IBM. Your point is still well taken though.

      --
      Dissolve... Resolve... Evolve...
    23. Re:FUD! by DarkEdgeX · · Score: 1

      I concede it was an awful anology. This is what happens when one posts on little sleep. ;) But the point is, any indication that Intel is conceding that 64-bit extensions to IA-32 at the way to go (rather than IA-64, e.g. - Itanium) would be fuel for AMD to use to sell their x86-64 based CPU's. "Look here, Intel is saying 64-bit exntensions are the way to go, and we've got them, now!" Intel won't have Prescott out the door for a little while longer, giving AMD an edge since x86-64 is here right now practically.

      --
      All I know about Bush is I had a good job when Clinton was president.
  28. Is Prescott 64-bit? by Anonymous Coward · · Score: 5, Funny

    No. It's just a really bad rounding error in the FPU.

  29. Re:It would almost have to follow AMD's convention by Anonymous Coward · · Score: 0
    Or there will be virtuly no software for it when it comes out and for months to come.

    There'll be virtually no software for the Athlon64 either, when it comes out. The 64-bit version of XP isn't even due until next year, so you'll have to run it in 32-bit mode if you want a Windows desktop.

  30. I'm still waiting... by TLouden · · Score: 1

    to see the games and media software optomized for 64bit before I upgrade. Right now (to the best of my knowledge) getting a 64bit proccessor wouldn't do anyting for me unless I was using it on a server with certain specialized applications. Otherwise it's just more money.

    --
    -Tim Louden
    1. Re:I'm still waiting... by drinkypoo · · Score: 1

      Yep, the software has to be recompiled for 64 bit before it will help you. If you're a linux user, you can get this benefit right now by compiling everything from source. (Other open-source Unices might also support x86-64 by now, but I'm too lazy too check.) There is a certain benefit to simply moving to the 64 bit ISA.

      If you're a Windows user, you have to wait for a 64 bit Windows to get any measurable benefit anyway, and unless everything you want to use is onboard, you'll have to wait for drivers too. They call it the "bleeding edge" for a reason.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:I'm still waiting... by Cereal+Box · · Score: 1

      Yep, the software has to be recompiled for 64 bit before it will help you. If you're a linux user, you can get this benefit right now by compiling everything from source.

      Wow, 64-bit grep, ls, bash, and xeyes -- imagine the possibilities!

    3. Re:I'm still waiting... by An+Onerous+Coward · · Score: 1

      The way I understand it, AMD's x86-64 architecture extends the original x86 architecture, so no recompilation is necessary. So even with no recompile, you still get a bit of a performance boost just from the fact that the Opeteron has more registers to play with.

      Of course, I learned it from Slashdot. So take it with a grain of salt.

      --

      You want the truthiness? You can't handle the truthiness!

    4. Re:I'm still waiting... by drinkypoo · · Score: 1

      The impression I got was that any benefit that 32 bit code saw from running on opteron was purely because the chip had a generally more efficient architecture. However what with temp registers and register renaming, athlon and pentium whatever chips (at least ppro/p2, but I would think basic pentiums as well? I'm not very familiar with p5's architecture at all) already have more registers than just the usual four. However the CPU does its best to just do the right thing with them, they are not (generally?) controlled by the program. There might be some way to poke around in there on some CPUs.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:I'm still waiting... by Anonymous Coward · · Score: 0

      Software can not use the new registers until it is recompiled.

    6. Re:I'm still waiting... by PurpleFloyd · · Score: 1
      How about 64-bit Apache, My/postgre SQL and all the other opensource server goodies? Not to mention a cheap way to accelerate science and math work for universities using in-house software. Oh, and then there's grep, which you even mentioned; its performance could probably be improved significantly by recompilation to take advantage of the new registers in x86-64, if nothing else.

      Cheap 64-bit server/workstation hardware has been way too long in coming; it looks like AMD is finally going to introduce some low-end competition into the market and force Intel to either slash Itanic prices drastically, put out its own lower-end 64-bit server/workstation chip, or simply cede a major server market to AMD (yeah, right).

      --

      That's it. I'm no longer part of Team Sanity.
    7. Re:I'm still waiting... by Anonymous Coward · · Score: 0

      Hmm..maybe you should have a look at the article on tomshardware.com (or was it Anandtech?) looking at the Opteron's benchmarking in gaming performance. Looks like the new AMD chips are a big improvement over the Athlons in 32 bit performance.

    8. Re:I'm still waiting... by yerricde · · Score: 1

      Still, even if the application software is not immediately recompiled, the system software can be recompiled to give a quick benefit. This will probably make a difference in I/O, graphics, full-motion video, and several other places.

      Besides, can't Gentoo users just recompile their whole system and apps by giving one command and going to bed?

      --
      Will I retire or break 10K?
  31. Its not the size, its how you use it... by f1ipf10p · · Score: 0

    Intel is strong on the prices this time. That was their strength when it was 8088, 8086, 8085 Intel vs. Motorola 6800. btw - back then AMD made chips for Intel...

    It will be interesting to see how the different CPU's make use of their wider data paths. My guess is that the VLIW (read Transmeta) approach will be very efficient. That alone is may not be enough. Never underestimate price point and marketing to determine a winner.

    Why don't ZILOG come out with a 64 bit? The Z640? :)

    --
    ~8^]
    1. Re:Its not the size, its how you use it... by calidoscope · · Score: 1
      Why don't ZILOG come out with a 64 bit? The Z640? :)

      Mmmmm. The real question is why didn't Zilog get the Z800 out in 1979? If they did, Zilog would probably still be a dominant manufacturer (as they were in the heyday of the Z80).

      --
      A Shadeless room is a brighter room.
    2. Re:Its not the size, its how you use it... by thisgooroo · · Score: 1
      The real question is why didn't Zilog get the Z800 out in 1979?

      i guess you mean the Z8000. they got it out, there were a couple of systems built around it (i remember olivetti offered a Z8000 system, also a few unix systems). the problem was that IBM chose to build the PC around the x86 architecture, which pretty much dried up the market for other 16 bit processors.

      Zilog also had plans for a 32 bit followup (the Z80000). i don't know why the never released that

  32. I've Heard This Before by MBCook · · Score: 5, Insightful
    I've heard this one before, and I've got to say it's an interesting idea. The way I heard the speculation was that Intel would launch Presscot as planned and that while it would contain the 64bit stuff, it would be turned off. Then if AMD hit it off with the Athlon 64, then Intel would tell mobo makers the secret code or whatever that would allow them to turn on the 64 bit part with a simple BIOS upgrade. All of a sudden, Intel would have an instant installed base of 64 bit chips. This means that if Intel doesn't use AMD's instruction set (I doubt this, as the article says it would be eating crow, they'd never do it), they'd have a good chance of instantly having a huge install base on desktop PCs, and since they are Intel, they could get software companies to follow. In one fell swoop they could win the 64 bit war.

    If Athlon 64 doesn't take off, Intel could keep things bottled up untill needed, or even nerver turn it on, letting consumers get 64 bit computing in a future chip that they've had time to improve the instruction set on or something.

    It really is an interesting idea, and quite a consipracy theory. Is it true? Who knows! But with all the hub-bub around the Opteron and the upcomming Athlon 64, I wouldn't be suprised if Intel were to drop a bomb like this soon. Just think. Intel first steals AMD's thunder by anouncing the P4EE. Not only is it announced first, but it trounces the competition in benchmarks (this is speculation, I haven't seen any numbers). If the P4EE is fast enough in benchmarks and the price is competitive with the Athlon 64, AMD could be in some trouble. Now if in a few months, Intel announces something like this, AMD's savior that they seem to be betting the farm on could be in BIG TROUBLE. If this happens, AMD's best hope is that Intel DOES use their instruction set, because if they don't things could get very ugly.

    So will any of this happen? Who knows! But that can't stop me from speculating! There is one last thing I'll comment on. If Intel does release a 64 bit processor soon, and doesn't use AMD's instruction set, there is a small possiblity that THEY (Intel) could be in trouble if the Athlon 64 (and friends) make a big enough splash. They might come too late to the party to make big decisions (like which instruction set rules).

    These things seem a bit more likely, given that Intel seems to be in trouble right now (IMHO). While they are ratcheting up the P4 fast, the fact is that they weren't planning on 64 bits any time soon, AMD has forced the issue on them. If AMD is right, that will put them in trouble. And anyone who follows this kind of stuff knows that Intel has some major heat issues. Current opterons put out what, 70 watts? And some of Intel's upcomming chips are looking at 120 watts during usage (maybe as high as 150 under full load). Between heat, stagnation, and pathetic sales of the Itanic, Intel seems to be in Trouble.

    The last thing that I'll say is a message to Intel: when you move to 64 bits (or even if you are just going to stick with 32 for a long time more)... DROP THE NAME PENTIUM. I'm tired of it. There have been FOUR of them (not counting all the different core revisions of each one). I know you have marketed that name for years, but it's time to move on. When will it stop? The Pentium 5, which you might call the Pentium Pentium, or Pentium Squared? Will I have to wait untill the Pentium 17 before you get a new name? Come one guys. Time for a name change.

    --
    Comment forecast: Bits of genius surrounded by a sea of mediocrity.
    1. Re:I've Heard This Before by Anonymous Coward · · Score: 1, Funny
      DROP THE NAME PENTIUM
      Um, Intel cannot advance beyond PENTIUM because the next in the series is SEXIUM.
    2. Re:I've Heard This Before by PD · · Score: 1

      They don't have to go in order. The next one could easily be eleventium.

    3. Re:I've Heard This Before by MBCook · · Score: 1

      Actually, it would be Sextium, I think. That said, I'd be a name with sex appeal! OK, in all seriousness, they could go to Septium, Octium (which the Lone Gunmen could steal), or anyting else. They could just go to names that aren't based one numbers (the Ueberterian chip, new for 2k4?). They have options.

      --
      Comment forecast: Bits of genius surrounded by a sea of mediocrity.
    4. Re:I've Heard This Before by Dominic_Mazzoni · · Score: 5, Insightful

      Then if AMD hit it off with the Athlon 64, then Intel would tell mobo makers the secret code or whatever that would allow them to turn on the 64 bit part with a simple BIOS upgrade. All of a sudden, Intel would have an instant installed base of 64 bit chips. This means that if Intel doesn't use AMD's instruction set (I doubt this, as the article says it would be eating crow, they'd never do it), they'd have a good chance of instantly having a huge install base on desktop PCs, and since they are Intel, they could get software companies to follow. In one fell swoop they could win the 64 bit war.

      You've got to be kidding. It takes years to develop a compiler for a new instruction set. If Intel suddenly announced that a lot of their chips were 64-bit capable, it would be completely useless, because there would be no software at all that could take advantage of it.

      Keep in mind that running 64-bit programs requires that the Operating System supports the instruction set completely (otherwise the registers wouldn't be saved properly, at a minimum), so they'd basically have to have Microsoft on board, in addition to probably a Linux port in order for it to be useful.

      And in the meantime, all of those extra instruction decoders and extra registers would be there on the chip, wasting valuable silicon that could be used for a larger cache. No way - Intel wouldn't sacrifice potential speed now for the chance to surprise everyone with a 64-bit processor later.

      Face it: Intel gambled with the Itanium, and so far their gamble hasn't been paying off. It's far too early to see who will win in the long term, but it's clear that the Itanium hasn't been an overwhelming success, while the Opteron is definitely equally popular already, if not already more popular.

    5. Re:I've Heard This Before by Wesley+Felter · · Score: 1

      Come on, we all know that -ium is tired; -ino is the way to go now.

    6. Re:I've Heard This Before by MBCook · · Score: 1
      You make a good point, but let's not forget that they have options. First it could be some form of the Itanic instruction set, which already has compilers (and even a version of Windows XP). Second, if Intel does this fast enough (or AMD adoption is slow enough) they could survive. Intel has compiler people, and maybe they're in kahootz with Microsoft. It's entirely possible that Intel could be doing this. When they turn it on, who's to say that they won't already have a bunch of companies ready to issue patches to their software to instantly take advantage of the new instruction set? They'd have a complier ready to go, they could have a port of Linux done, etc.

      They're Intel. If they suddenly have the lead in the 64 bit game overnight (as might happen depending on adoption rate), then combine that with their clout in the industry, and who knows what they could do. I think they could pull it off. If they announce at 10:00 AM PST that all shipped Presscot processors can now be 64 bit processors with no performance hit (actually a gain) for free (just a BIOS update), I bet they could have MS announcing a update to Windows (or a new version of XP for the processor) that's complete by 11:00 AM.

      I think that Intel would try to cram the Itanic instruction set into the desktop before they'd take AMD's instruction set unless they get thouroughly creamed in the market and are forced to just to try to survive.

      --
      Comment forecast: Bits of genius surrounded by a sea of mediocrity.
    7. Re:I've Heard This Before by Groo+Wanderer · · Score: 1

      Think less of the conspiracy theory, and more towards what they did with Jackson technology. The very first P4 cores had a crappy version of Jackson, and it wasn't turned on. Those who managed to hack it on quickly realized that it wasn't all there yet.

      I am pretty sure intel will do the same with the 64 bit functionality. They will at least have to wait until socket 775 makes it out before they start, the pins I was talking about are not there until those chips hit, so it is a moot point.

      As for the power useage, AMD has a hard limit of 89w for any K8 cored CPU on a .13SOI process. They are nowhere near that, and since they just enabled the really advanced power management in the C stepping chips, they are even more efficient.

      If you look at another of my IDF articles:
      http://www.theinquirer.net/?article=115 88
      You will see what Intel has in store for the next 3 P4 generations. 125A?!? Holy shit.

      -Charlie

    8. Re:I've Heard This Before by Aadain2001 · · Score: 1

      But is it more popular because it is technically better, or is it because it is coming from the underdog AMD? People love rooting for the underdog, hence why people love AMD. It's been a while since they've had a good quarter, and if things don't improve for them and fast they will fail as a business.

      I think that their answer to 64 bit computing is a "patch" at best. They are trying to bring the x86 world into 64 bit computing when it's really to wrong answer. Extending the x86 architecture is a mistake. It needs to be completely scrapped and started over, hence why Intel designed the Itanium. I'm not saying that the Itanium is the end-all-be-all for 64 bit computing, but the basic idea is the right one. Take the opportunity of the 64 bit upgrade to start from scratch. Fix all the aspects of the x86 instruction set that caused all these CPUs to take so many transistors and die space. Intel knows this, that's why they are investing in the Itanium line instead of just changing their ALUs and FPUs from 32 bit to 64 bit and from changing the size of their registers. That's more of a hack than a solution from a technical stand point.

      Will AMD's answer to 64 bit suceed? I a word, no. Some will adopt it, but mainly it will only be the AMD fanboy types, both in the home and in the fringe technical world. Those who have to worry about more than supporting their favorite underdog will look at the Opteron from a technical stand point and see the same thing Intel has seen. It is a simple hack to extend x86 into 64 bit computing, not a true jump from 32 bit to 64 computing. The ability to address more than 4 GB of memory is nice, and more general registers is also welcomed, but there is not great advancement in computing from the Opteron.

      --
      Space for rent, inquire within
    9. Re:I've Heard This Before by drinkypoo · · Score: 1

      Intel could be developing their own 64 bit compiler for this processor, and they could be working on support for it for gcc. I'm not saying it's likely, but it's possible.

      However, hammer is cheap, truly 64 bit, and it's here and supported by free software now. All it needs is windows. And it's going to get cheaper in a few days, too, although athlon 64 doesn't have MP support, which makes me not want to buy it. I want my next workstation to have two processors in the same way that I want my next car to have AWD :)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    10. Re:I've Heard This Before by Anonymous Coward · · Score: 0

      They're going to call the next one "Whistlehorn"

    11. Re:I've Heard This Before by Slack3r78 · · Score: 1

      I may be mistaken, but I seem to remember having read at one point that the Athlon64 would support a dual processor setup. Thinking about it, it makes sense since it's rumored that the AthlonFX line will just be rebranded Opterons anyway. Might be worth checking out.

    12. Re:I've Heard This Before by drinkypoo · · Score: 1

      Yeah, originally the Athlon 64 (whose name was not yet determined, and which was being referred to as "clawhammer" at the time, while opteron was "sledgehammer") was supposed to have two HT buses per processor. One for communication with the chipset, and one for communication with another processor. In addition each one would have a single channel memory controller so in effect you would have a dual channel memory controller. (Obviously it's not exactly as good as a dual channel memory controller, and there are some cases in which it won't be as fast as if you did, but most of the time it would do just fine.) But they pulled one HT bus, and so we got the gimpy version. The only difference between clawhammer and sledgehammer, really, is that sledgehammer has more HT buses and... I can't remember, IS it getting a dual channel memory controller? Anyway, and that sledgehammer has more cache. So, you have a larger part with higher power dissipation and a lower yield, naturally it's going to cost more and have higher cooling requirements, plus it needs more pins, thus a larger package. All of this has come to pass. Meanwhile we'll apparently end up with an Opteron with less cache for our Athlon 64 MP equivalent, whatever it ends up being named. (That would be my choice, actually, for continuity.) With less cache it will have higher yields than Opteron, so even in the larger package it will still be more reasonably priced.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    13. Re:I've Heard This Before by IM6100 · · Score: 1

      Well, Alpha is cheap, truly 64 bit, and here and supported by free software too.

      It used to have Windows....

      --
      A Good Intro to NetBS
    14. Re:I've Heard This Before by drinkypoo · · Score: 1
      Cheap? Surely you jest. And yeah it used to have windows, but no apps to speak of. Great if you wanted to play solitaire really quickly, I guess. It is supported by free software, though. Okay, so you can get cheap alphas, but they're butt slow. I was just poking around and you can get an all in one motherboard with your video, sound and so on, with a 1.1GHz Duron chip, for $69. You can build a PC out of that for $200 that will spank the hell out of an Alphastation 3000/300X (175MHz) for example, which will still run you a hundred or two. So why bother, unless you actually need 64 bit for something, in which case, the ram you'll probably be needing for your application will cost more than a cheap alpha.

      The Opteron, on the other hand, needs only a minimal software compatibility layer to run 32 bit code on a 64 bit OS.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    15. Re:I've Heard This Before by Anonymous Coward · · Score: 0

      You've got to be kidding. It takes years to develop a compiler for a new instruction set. If Intel suddenly announced that a lot of their chips were 64-bit capable, it would be completely useless, because there would be no software at all that could take advantage of it.

      Why do you assume Intel hasn't been working on a compiler for years in secret?

    16. Re:I've Heard This Before by Anonymous Coward · · Score: 0

      they have to make it public for other companies to modify their programs. updating programs to take advantage of 64 bit processing is not a simple task. no company is going to do it based on rumors. it makes more sense if Intel announced it before the release and becasue that is more likely to persuade companies from following AMD's processor. if they had that processor, they would have already announced it. they did not most likely because they don't.

    17. Re:I've Heard This Before by Anonymous Coward · · Score: 0

      It may be a hack, but it's a beautiful one.

      x86 may not be pretty, but CPU makers have become so good at working around the limitations that there really is very little to gain by moving away from it.

      I don't have any figures, but I'm sure the x86 "baggage" doesn't add much to the die space in modern processors, where most of it is cache anyway. Itanic has a huge die BTW, compared to x86 CPUs.

      The problem with starting from scratch is that most users (specially home users) won't upgrade to something that can't run their old software faster than their old system. I know I wouldn't want to...

    18. Re:I've Heard This Before by BlueBiker · · Score: 1

      You obviously haven't looked very carefully at the AMD64 ISA. In the eyes of many observers, AMD has made quite a number of inspired decisions in the design of their 64-bit architecture. While technical purity may be desirable from an esthetic viewpoint, they've done an excellent job of providing the machine resources most needed by executing programs while eliminating those which were expensive to provide and rarely needed.

      One of the [accidental?] virtues of x86 code, especially as compared to RISC or VLIW/EPIC, is its high density. While decoding it is a pain, its compactness takes very good advantage of available cache space and memory bandwidth.

      Besides which, releasing a totally incompatible 64-bit ISA wouldn't make sense. Nobody would buy such a consumer chip if it didn't run their existing Win32 software, which will take time to be recompiled for any new architecture. Athlon64 and Opteron run IA32 very competitively without needing any type of emulation, and the decade-long investment in IA32 code generation technologies can be used as a jumping off point for efficient AMD64 code generation, as contrasted with Intel's continuing difficulty to provide efficient compilation for IA64.

      You can keep talking about hacks and patches, but in the real world AMD64 is one helluva powerful design.

    19. Re:I've Heard This Before by lxs · · Score: 1

      Well, actually, the next in the series would be HEXIUM, which would be even worse than sexium in PR terms.

    20. Re:I've Heard This Before by juhaz · · Score: 1

      Not really, i686 (ppro and it's derivatives) would've been sextium, but that series is already dead and buried.

    21. Re:I've Heard This Before by Lawrence_Bird · · Score: 1

      >They are trying to bring the x86 world into 64 bit computing when it's really to wrong answer.
      >Extending the x86 architecture is a mistake. It needs to be completely scrapped and started over,
      >hence why Intel designed the Itanium.

      one word mate: COBOL

      don't mess with the installed base

    22. Re:I've Heard This Before by maraist · · Score: 1

      Itanium / x86 instructions sets are ALREADY merged. That was the whole point (originally).. There is a "jump-to-x86-instruction" itanium op-code which allows you to run "legacy" subroutines/libraries. The original Itanium simply emulated x86 instructions though (poorly at that).

      So what you're really suggesting is to take a Pentium 4 core, and "emulate" IA-64, via a "jump-to-ia64-instruction".

      This is a highly non-trivial task, because IA-64 has COMPLETELY different assumptions about hardware resources (128 regs of both int/fp), as well as rotating registers (a la sparc), which means more than 1k total registers (all 64bits). While many of the registers can be reused as castrated x86 register-renameables, it's not likely to be possible to optimize register access for BOTH reg-renaming and direct reg-access.

      Intel had the option of trying to optimize x86-32 for upcoming itaniums, but last I heard, they were merely going to throw a P4 onto the motherboard to run legacy apps (a la co-processors).

      Frankly, I think that's the correct solution; they should have worked co-processor instructions into IA-64 from the beginning. At the prices of these systems, heterogenousness isn't going to be a major additional factor.

      That being said, I don't see a viable Itanium -> x86 merge.

      --
      -Michael
    23. Re:I've Heard This Before by EddWo · · Score: 1

      It's interesting that they are going to call it

      Microsoft(R) Windows(R) XP 64-Bit Edition For 64-Bit Extended Systems

      rather than AMD64 systems or x86-64 systems. Perhaps it does contain something Intel specific as well.

      --
      "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
  33. Re:I wouldn't buy the Athlon anyway by Unregistered · · Score: 1

    uh... most laptops don't work well in the lap. I can't use my p3 in my lap. Hell, people even say you can't use Macs in the lap. Computers get hot, it's a fact of life. for a cool laptop you're probobly gonna need a transmeta.

  34. 64-bit by be-fan · · Score: 4, Interesting

    I don't know if this "dual 32-bit" thing is very plausible. Being able to do 64-bit operations is perhaps the most useless feature of the upcoming 64-bit processors. The big things about AMD64 is the larger compiler-visible register file and the ability to address > 4GB of memory.

    --
    A deep unwavering belief is a sure sign you're missing something...
    1. Re:64-bit by Anonymous Coward · · Score: 0

      "Being able to do 64-bit operations is perhaps the most useless feature of the upcoming 64-bit processors. "

      You apparently don't run any scientific codes that use doubles instead of floats. If you have an equal number of registers, 64bit gives you 2x as much data on chip.

    2. Re:64-bit by be-fan · · Score: 1

      And you obviously don't know how a CPU works. Current 32-bit x86 CPUs have 80 bit integer registers (for long-double). The P4 has 8 128-bit SSE2 registers for doing 4 32-bit or 2 64-bit operations in parallel. None of the proposed 64-bit extensions do anything to the size of the floating point registers, and the AMD64 extensions only add 8 additional *visible* SSE2 registers, without changing the size of the internal register file.

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:64-bit by p3d0 · · Score: 1

      We're talking integer registers here. Everything since the x87 has already supported doubles.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    4. Re:64-bit by Anonymous Coward · · Score: 0

      Your missing the point, it is the 64 bit that enables the AMD64 to cleanly address memory above 4GB. Intel might shake some dust off of the Intel Above Boards to satify the need for more than 4GB but performance was bad with extention technologies like that.

      Get 64 bit and > 4GB RAM now with AMD. It even has an OS for it!

  35. Re:BAH! 286 is all you need. by carsont · · Score: 2, Informative

    As far as I know, the UltraSPARC made its debut in 1995, while the first 64-bit Alpha from DEC was announced in 1992. 64-bit MIPS and PA-RISC chips were probably sometime between those two dates. See here.

    --

    Ubi dubium, ibi libertas.
  36. Re:I wouldn't buy the Athlon anyway by Jason+Zaman · · Score: 1

    the normal athlons were really hot but the new Opteron chips even when they are overclocked are still colder than anything by intel

  37. Re:I wouldn't buy the Athlon anyway by jejones · · Score: 1

    Sure. Aside from the first PClonish computer I ever had (a NexGen, and since AMD bought them and used the technology in the K6 and Athlon, even that is arguable in a way)--and a Cyrix long ago, come to think of it--all the PClones I've bought have been AMD-based. Counting hand-me-downs, that would be half a dozen, four of which are sitting within a yard and a half of me as I type, churning merrily away.

  38. Re:I wouldn't buy the Athlon anyway by Malor · · Score: 4, Informative

    Athlon chipsets sucked rocks for a long time, and were really unstable. But VIA finally got their act together, I think with the KT133A.

    AFAIK, other than stomping on occasional driver bugs, Athlon chips have been pretty excellent ever since. I have an Athlon 1900+ on an ASUS A7V333 that's rock solid, and a new Athlon 2500+ on an Nforce2 board that's not quite as solid, but which is still pretty good.

    I'd like to see some improvements on the NForce2 chip stability. It's not all the way there yet, in my opinion. But the VIA chipsets are extremely solid.

  39. Re:Nigger Owner's Manual (GPL) by unassimilatible · · Score: 0, Offtopic

    This is why my Web site doesn't have a message board.

    --
    Slashdot "libertarians": Small government for me, big government for those I disagree with. -1, I disagree with you
  40. Isn't this what Intel wants? by Kevinv · · Score: 5, Insightful

    Float a rumor that their next chip wil have some 64 bit instructions, so don't upgrade to that competitor that is true 64-bit?

  41. Re:It would almost have to follow AMD's convention by Anonymous Coward · · Score: 1, Interesting

    It seems to me that they would probably go with an instruction set that is semantically isomorphic to AMD's, but uses slightly different opcodes. This way you could get a compiler to target the new architecture just with only modifications to the assembler, leveraging the existing effort to port software to the AMD 64-bit architecture, and AMD could easily release a new generation of chips supporting both opcode formats, making the "Intel" x86-64 architecture a standard. And AMD would probably do this if the Intel processors are successful, because they could become marginalized otherwise (even if their's was first!).

  42. Re:I wouldn't buy the Athlon anyway by yomegaman · · Score: 2, Insightful

    I have a Centrino-based Acer and it rarely gets even noticeably warm. Intel may have screwed some things up but they got the Pentium-M right.

    --
    ...wearing a skin-tight topless leather jumpsuit, with cutaway buttocks and transparent crotch panel.
  43. WTF? by sinserve · · Score: 2, Insightful

    The article doesn't mention "64-bit" anywhere. Where did this sensationalist
    "reporter" pull his news from?

  44. Erm... by JayBlalock · · Score: 1

    ... someone with points mod the PARENT up. Although if you'd like to share with me, that's cool too.

    --
    Bush: He's Liberal in all the wrong ways.
  45. Um by Anonymous Coward · · Score: 0

    Why is this marked troll?

    1. Re:Um by Anonymous Coward · · Score: 0

      Because it IS a fucking troll. Geddit?

  46. Re:I wouldn't buy the Athlon anyway by Anonymous Coward · · Score: 0

    I haven't had any problems with my AMD processor computers, and those are the only ones I've bought since 1998 [6 of them]. A lot of AMD complaints I hear are about AMD's noise, which is quite silly considering that the processor itself doesn't make any noise, for some reason people just seem to buy noisy fans for their Athlons. My AMD box at home [1.4ghz duron] has a 26dB fan and has run smoothly for ages.

    Two AMD based servers I bought last year have been running without any problems from the day they were installed on their racks and powered on, over 400 days of uptime on them.

    I'm not really an 'AMD fan', but I've just noticed that buying AMD gives me more performance for less money, so I see no reason to buy anything else, especially when I have had zero problems with the processors so far.

  47. Temps by Anonymous Coward · · Score: 1, Insightful

    "Intel's new Prescott has 64 bit instructions lurking inside. Could really rain on the parade of those who thought the new Athlon 64's would be supreme - especially when you look at Intel's price roadmap. Don't run out and buy an Athlon 64 just yet..."

    This is the Prescott with the 103W Thermal Dissipation? Will we still hear people complaining that their 68W AthlonXP turns their room into a sauna?

    Do you not think AMD will match or better those prices?

    WHy would it rain on their parade? It would simply mean that software would be ported much more quickly if Intel announced that they were implementing AMD's x86-64 architecture. There is no way they could start a different architecture, Intel-x86-64 would be a flop.

  48. Re:I wouldn't buy the Athlon anyway by Kenja · · Score: 1

    Is that the same KT133A that couldnt post if you had a SCSI card and a PS2 mouse installed at the same time?

    --

    "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
  49. Re:gotta compete by Waffle+Iron · · Score: 3, Informative
    But look at the PC architecture...the same outdated CISC architecture that was used in 1981 is still there in today's PC's.

    You do realize that there has been no such thing as a "CISC processor" since the Pentium Pro came out. Underneath the X86 bytecode VM, Pentium IVs, Athlons, etc. are highly advanced RISC cores with multiple concurrent execution units.

    The main reason that the huge expensive power sucking Itanium scrapes out a small lead in benchmarks over X86 CPUs is because of its expensive huge power sucking cache.

  50. Re:I wouldn't buy the Athlon anyway by Sillypuddy · · Score: 0

    I have over 7 athlon pcs myself and have sold/assemble numerous others.

    They all work without any problems. Can't say the same with my friend's P4. It runs hot and the 865PE motherboard is unstable.

    -joe

  51. Re:I wouldn't buy the Athlon anyway by CaptBubba · · Score: 1
    As noted by yomegaman the P-M is much cooler than the previous laptop processors.

    Actually, while my P4-M 1.6GHz laptop does get hot under load, most of the heat on the bottom comes from the DDR memory and mini-PCI 802.11b. All the CPU heat goes out through the back of the laptop.

    speaking of laptops in the lap, when I purchased my PCI 802.11b card for my desktop it had a warning on it to keep the antenna 15cm away from your body. Not only are my laptop's antennae less than 2cm to my body when the laptop is in my lap, they are rather close to some parts of my body that I don't want irradiated. Should there be a warning on laptops: "do not use in lap if 802.11b is in use"?

  52. Re:Grrr... by RobKow · · Score: 1

    The UltraSPARC III isn't exactly the fastest CPU around; it gets thoroughly trounced by the P4, Athlon XP, MP, and POWER4, among others. We'll have to wait and see until the dual-core Ultras come out early next year.

    Still no instruction reordering...

  53. In honor of my first computer... by TimeForGuinness · · Score: 4, Funny
    I think AMD should change its chip's name from Athlon 64 to the Commodore 64 .

    AMD should kick it Old School.

    1. Re:In honor of my first computer... by sjwt · · Score: 1

      might as well put this in thread..
      was just thinking of the fun of
      emulating a C64 on an AMD64.

      well it brings funny visulsations
      to my mind..

      I see a C64 travling down the bus,
      and geting mashed though the processor :0

      --
      You have 5 Moderator Points!
      Which Helpless Linux zealot/MS basher do you want to mod down today?
  54. Has anyone Considered? by Bruha · · Score: 4, Insightful

    What would happen if they succeded in causing AMD to go out of business? Then the only other option for consumers are VIA C3's and Transmeta which will never match Intel's. So then once again at the top of their game and after buying auctioned assets off AMD's corpse they ratchet prices back up and we lose out on innovation.

    1. Re:Has anyone Considered? by Anonymous Coward · · Score: 0

      IBM has a nice chip, I hear those mac nerds yap about it all day.

    2. Re:Has anyone Considered? by newbiescum · · Score: 1

      I don't think Intel really wants to drive AMD out of business. It's better to have a known adversary than one that comes out of nowhere. Also, it helps to have some viable competition (just not one that gets too big) that way your company doesn't just sit and rot with no goals. If there wasn't any competition, the day that another company comes out with something better, you're at a loss at how to fight them.

    3. Re:Has anyone Considered? by Anonymous Coward · · Score: 0

      Having a compeditor doesn't guarentee that they won't be blindsided together.

    4. Re:Has anyone Considered? by pmz · · Score: 1

      Then the only other option for consumers are VIA C3's and Transmeta which will never match Intel's.

      Only for people tied by the balls to x86-only platforms like Windows. Windows on Itanic is rare enough to make it inconsequential.

      Thus, we see an advantage of Open Source coupled with GCC and POSIX runtimes.

  55. Pah. by BJH · · Score: 3, Insightful

    Can you say "astroturfing to ruin the release of Athlon64 coming up next week"?

    I knew you could!

    1. Re:Pah. by Anonymous Coward · · Score: 0

      I'm with you 99%.

  56. PreSCOtt by KoolDude · · Score: 4, Funny


    In other news, SCO sues Intel for the use of their na... SLLLLLLLAAAAAAPPP!!!

    Ouch, that hurt!

    --
    getSexySig(); /* returns sexy signature */
  57. Re:gotta compete by Anonymous Coward · · Score: 2, Interesting

    Underneath the X86 bytecode VM, Pentium IVs, Athlons, etc. are highly advanced RISC cores with multiple concurrent execution units

    But the instruction set still hobbles the design in many ways. The logic to convert x86 instructions to micro-ops takes up space on the die and uses extra power. And any way you look at it, you have to read from memory a lot more often with 8 "general purpose" registers than 32 real GPRs, which is what most sane CPUs have. Itanium doesn't have to do this, PowerPC doesn't have to do this, no modern ISA requires this nonsense. Sure they may have figured out how to get it to run fast anyway, but this is wasted time: Intel should have been able to transition desktop PCs to the i960 in the early nineties, and we would probably be making a trivial upgrade to a 64-bit extension of it just about now. The processor would have all the fancy performance-enhancing features of a modern P4, but would not be held back by the need to emulate a 286.

    The main reason that the huge expensive power sucking Itanium scrapes out a small lead in benchmarks over X86 CPUs is because of its expensive huge power sucking cache.

    It doesn't just "scrape out a lead" in floating-point benchmarks, it absolutely destroys the x86 competition. And oh yeah, its running at what, half the clockspeed of the P4? If Itanium had the same economies of scale behind it at this point, there would be no competition.

  58. Because slashdot practices free speech thats why by Anonymous Coward · · Score: 0

    Because slashdot believes in free speech unlike stupid hitlers like yourself. Chump.

  59. FUD by babbage · · Score: 1, Insightful
    Don't run out and buy an Athlon 64 just yet...

    Is the submitter an employee of Intel? Isn't this classic FUD tactics? "Wait, don't buy that guy's product, we're coming up with something even more super duper in just a few months...".

    I smell a rat.

    There may be nothing malicious to this, but the specific exhortation not to buy a competitor's product just because of the possible future abilities of some other company's products just turns me off. Of course they're all going to have something better in six months, a year, a decade, etc.

    The only way to make sense of it all is to compare apples to apples: the Althon64 & PowerPC G5 are both on the market now, or about to be, so comparisons there are valid. Comparisons to what Intel might possibly be making later are just... well, they seem very questionable to me.

    (And since I've been pointing fingers willy nilly, I have no vested interest in whether Intel or AMD does better in the market. I mostly use Macs and am indifferent to who has their brand name on any x86 hardware I might use to run Linux...)

  60. this scares me by nuckin+futs · · Score: 2, Interesting

    MS has been long rumored to tell Intel what they can and can not do, and their record in confrontations like this are not one to bet against. Rumor has it that the vole has said that they will only support a single 64-bit extension to IA32, but then months ago they said they would be supporting 5 64-bit architectures in windows.

    does this mean the chip will be tailored for the MS OS?
    will it be totally worthless if you buy a system and load a different OS?

    1. Re:this scares me by mabinogi · · Score: 1

      Athon64
      Opteron

      Itanium
      Itanium II

      There we have 4 64 bit CPUs (ok, not architectures, but still 5) in two groups, 1 64bit extension to IA32, and one complete new ISA - IA64.

      The 5th one could be this supposed 64bit Pentium - which would be using either x86-64 (unlikely), or IA64. Or maybe they just mean Duron64 (or whatever the eventual budget Athlon64 gets called)

      so both can be true, and no secret special MS only CPU.

      Personally I find the prospect of a secret 64bit Pentium rather unlikely, but I guess we'll have to see. I'm not going to avoid Athlon64 because of a rumour, if it's cheaper than a pentium and performs at least as well as one, I'll buy it, 64bit capability isn't going to gain me anything.

      --
      Advanced users are users too!
    2. Re:this scares me by lxs · · Score: 1

      does this mean the chip will be tailored for the MS OS?


      Wheee! Hardware accellerated worms!
  61. 64 bit doesn't matter YET by eagl · · Score: 2, Insightful

    64 bit... who really cares RIGHT NOW? The Athlon 64 appears to be posting up a very nice showing with today's apps and games, so the processor you buy tomorrow morning ought to be the one that will run your programs the best today and next week. Next month and next year... Bah. You can drive yourself crazy trying to lead-turn the chip industry. Get a cpu with "hidden 64 bit inside" and by the time any software is written to take advantage of it (meaning it actually runs faster than before), there will be another cheaper cpu already available that once again runs "today's" programs faster. If you need bleeding edge performance at any cost, go ahead and buy the latest cpu every 3 months and be happy. If not, buy the best bang/buck AT THE TIME OF PURCHASE and just accept that you may want to upgrade 6 months from now. 40-50% of the price will buy you 80-90% of the performance of the top cpu out there, so that makes it a lot easier to afford an upgrade that will leapfrog past what used to be the top cpu at the time of your original purchase.

    Buying a cpu for applications more than 3ish months away is a foolish decision. The price and product cycles makes buying those capabilities ahead of time a bad idea. You only have to look back at the early pentium adopters to realize what a little patience can do for you. Back then, a fast 486 would hands-down beat a pentium in any application except for a couple of image editing apps, and things stayed that way for months. Things stayed that way for nearly a year until Intel nearly doubled the speed of the pentium, finally putting the 486 out of the picture. A 64 bit processor better be damn fast today or it shouldn't be purchased. By the time the extra performance seen from 64 bit apps and operating systems is realized, you'll be able to buy an even faster/newer cpu for less money. Save your pennies and get what works the best today.

    For what it's worth, TODAY the fastest cpu seems to be an Athlon64 or Opteron. Hidden 64 bit instructions won't change that a bit. Show me the application benchmarks and I'll believe. Until then, I'm saving my coin for the next upgrade cycle.

    1. Re:64 bit doesn't matter YET by p3d0 · · Score: 1
      A 64 bit processor better be damn fast today or it shouldn't be purchased.
      Well, good thing the Athlon 64 will be damn fast.
      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
  62. No, it isn't by Groo+Wanderer · · Score: 5, Informative

    As the author of the article, I had to REALLY make things vague. The people involved would be hurt badly by Intel if their names got out. Some of the situations that were told to me make it quite apparent who was leaking. That was as specific as I could make it :(.

    -Charlie

    1. Re:No, it isn't by Anonymous Coward · · Score: 0

      Come on, you're just a regular jackass, pulling stories out your anus. This story reflects badly on you, really.

    2. Re:No, it isn't by Anonymous Coward · · Score: 0

      Yeah, sure, whatever. Unsubstantiated rumors to get your name in the bylines while the real journalists wait for facts. Typical tabloid pap.

  63. Re:gotta compete by EastCoastSurfer · · Score: 2, Informative

    gotta compete. Intel had to come with something better(cost effective) than Athalon64. If there was no competition, we would be still using 8088/6

    LOL, Intel is actually their largest competitor. Every time they release a new chip guess who they are primarily up against? People who are running other Intel chips.

    Without AMD though, I'm sure Intel would keep their new chips at higher price points for a bit longer and milk the power user crowd for a little more money.

  64. Whatever... by Anonymous Coward · · Score: 0

    They are fools to rush a release like this. Intel should have just done it right. Every product has it's time. When a product isn't ready for the marketplace it isn't ready. Don't rush it Intel.

  65. There is another Chip-Architect article by Groo+Wanderer · · Score: 1

    There is a second article on Chip-Architect that goes into the 64-bitness in greater detail. I also linked to a few other sources. People keep talking about the exec bit that I had to make vague so the person who told me wouldn't get nailed. Take it as you will, but there is absolutely no doubt in my mind.

    -Charlie

  66. Re:I wouldn't buy the Athlon anyway by malkavian · · Score: 3, Interesting

    I'll stick with Intel, thanks. Any of you guys actually have a *good* AMD processor?

    Well, I've got the old K5PR133 sitting on a shelf now that did years of sterling service, first as my main desktop CPU, then moving back to the firewall CPU, until it got replaced by the K6 II 350 (which is still in the firewall machine, and has been there, running solidly, day in, day out since about 1999, and was my desktop CPU before that,replacing the K5).
    Replaced the K6 II with an Athlon 700 (original slot A). That ran fine, until the board fritzed, due to the old capacitor problem that ran rampant in late 99, early 2000.. The board lasted until 2002. The only reason it's not in the firewall box now is that I can't get another board for less than it'd cost to put a faster athlon in a cheap board..
    The 2002 set I bought was a nice Athlon 1700 in an Abit board. Ran stably and never a problem.. That's now in the girlfriend's machine (built one for her from the last generation of hardware I had lurking), and now I'm using an NForce2 board with an Athlon 2500 (Barton core).
    No problems with any of them.

    If the college computer broke, are you sure it's the CPU? Not memory, motherboard, power supply or any of a myriad of other issues?
    For the laptop, is it a problem with the manufacturers not putting good cooling and airflow in the laptop (or, heaven forbid, a desktop CPU in a laptop case to save money/add a little extra speed)?

    By all means, stick with Intel if it keeps you happy, but I've had a long history of using AMD chips, and I like 'em. If I saw a reason to use Intel's chips, I would.. I just never have to date...

  67. Re:FUD-mod parent up by Ralph+Spoilsport · · Score: 1
    As the other poster noted: this is just more scare tactics and FUD from Intel. Having some 64bit parts doesn't make it a 64bit chip., nor does their roadmap necessarily mean that AMD is going to be out priced and outperformed - I didn't see anything about AMD's roadmap...

    Mod the parent up. He wasn't very articulate, but he was right on the money.

    RS

    --
    Shoes for Industry. Shoes for the Dead.
  68. Re:Aah! My 64-bit Prescott! by Anonymous Coward · · Score: 0

    From the Timothy is working for Intel department..

    Biased as hell, seems this news post.

  69. The Inq by zealot · · Score: 2, Insightful

    The guy who started The Register (Mike Magee) left and started The Inquirer. So, it's not really a wanna-be...

    --
    He said, "You'll be able to tell your grandchildren that you helped assemble the first NT supercomputer," and I cringed.
    1. Re:The Inq by DarkEdgeX · · Score: 1

      Yeah no kidding, that was the most misinformed comment I've ever seen. And of course, it got modded up as it deserved!

      I read both, but Mike Magee is what made The Register what it was, nowadays when looking for CPU news I tend to follow The Inquirer more. Le Reg is still good for other stories, but ever since he left, their CPU-specific content has been hurting, heh.

      --
      All I know about Bush is I had a good job when Clinton was president.
    2. Re:The Inq by IM6100 · · Score: 1

      Kinda like when Al Shugart quit Shugart & Assoc. and started Seagate, eh? And those pesky Palm engineers who started Handspring....

      --
      A Good Intro to NetBS
  70. Look to the G5 by Groo+Wanderer · · Score: 2, Informative

    A really good example of what you are talking about is the G5. It simply extends an efficient architecture to 64 bits. Other than upping the memory limit, it does precious little to performance. The chip in 32 bit more is about as fast as 64 bit, and only starts to show a difference when memory useage gets large.

    As for AMD, you can see the effect by running a program in 32 bit mode, then running a 32 bit program recompiled to take advantage of the registers in 'compatibility' mode. There is quite a difference.

    -Charlie

    1. Re:Look to the G5 by Flywheel · · Score: 1

      The difference between the PPC ISA and the x86 ISA (Specifically the AMD64) is that the PPC ISA from the beginning was 64-bit, but with a - well - 32-bit extension .... remember that the PPC ISA is a proper subset of the Power ISA ... it is rather astounding that the PPC has not become 64-bits sooner (Not including the 620)....

      --
      Live long and prosper...
  71. Comparison with Apple's G5 by Mr.+Ophidian+Jones · · Score: 3, Interesting

    People just assume that G5 consumes this enormous amount of power because of all the fans in the G5 desktop. This isn't true. Even the 2G takes only about 40 watts or so. One P4 3G takes in the range of 80 watts of power. All of the extra G5 fans are to make the cooling quieter.

    I'm glad to see someone finally point this out. The exact wattage number is 46.7 watts for the 2 GHz PowerPC 970 "G5" running at full speed (2GHz CPU and a 2:1 multipler for a 1 GHz FSB).

    A 2.4 GHz P4 (400 MHz FSB) uses 62 watts, newer P4s use even more. Prescott is expected to use 100 - 105 watts. (And this is totally ignoring the even further power needs of the "extreme" edition with its added transistors for on-die L3 cache)

    Apple has always seemed to overengineer the heatsinks and fans in their desktop model, for about as long as I can remember. Oddly, many of the PowerBooks use a much different "transfer the heat from the CPU, Chipset, and GPU right to the bottom of the case" cooling method.

    1. Re:Comparison with Apple's G5 by addaon · · Score: 1

      Cache uses very little power, all things considered. This is why the Pentium M is so cache heavy; it's the lowest power way to increase performance, although not the fewest-transistor way. (Also note that the power architecture of the Pentium M's cache is seriously cool.. at the cost of an additional cycle of latency for L2 access, three quarters of the cache uses basically no power at all times. I'd give my left foot for IBM to license/use that in the 750GX.) Also, keep in mind that the G5 is meant for dual processor machines, meaning ~95 processor watts high end. The P4 is for single processor boxes, giving ~105 watts high end. This is not so big a difference, and the power-hungry chipset on the G5 probably comes close to making up for it. The G5 is a much better engineered machine, in my personal opinion, and seems to get a lot more for its watts... but the power consumption of a high end G5 and a high end Prescott should be pretty damn close to identical.

      --

      I've had this sig for three days.
    2. Re:Comparison with Apple's G5 by RzUpAnmsCwrds · · Score: 0

      The parent has been posted before, verbatim, by another Slashdot user.

  72. Actually, do go get that AMD or IBM chip by droleary · · Score: 2, Informative

    Don't run out and buy an Athlon 64 just yet...

    To anyone that 64 bits might make a difference for, they're steering clear of Intel, who has stated they're not going to focus on that desktop market for another 5 years. So all this article amounts to is Prescott FUD to support Intel's (misguided) roadmap.

    Disclaimer: I own some AMD stock and I do my Unix development on Mac OS X.

    1. Re:Actually, do go get that AMD or IBM chip by ProtonMotiveForce · · Score: 1

      Umm, 64-bits on the desktop is a ways off. You hear nerds claiming they want it, but they don't really know why.

      Let me give you a hint: You'll need 64-bit processors on the desktop exactly when you see average machines with 3-4 gigs of memory. Not before.

      I'd lay wager that the average power-user/enthusiasts machine right now has 1 Gig, or 2 Gigs for the hard-core (who probably don't use more than 768 megs of it). The average _new_ desktop probably has 512 megs.

      Now you can prattle on about how much easier it is to write software with 64-bit processors, but it's silly. The software's written. It's too late. In fact, it takes _effort_ to port to 64-bits. So that's a non-argument.

      Really people, think about things before you start jumping on bandwagons.

    2. Re:Actually, do go get that AMD or IBM chip by droleary · · Score: 1

      Umm, 64-bits on the desktop is a ways off.

      Umm, no, since I can get a G5 Mac today.

      You hear nerds claiming they want it, but they don't really know why.

      Sounds more like you don't understand their reasons rather than them not understanding. That just means you don't (think you) need 64 bits.

      Let me give you a hint: You'll need 64-bit processors on the desktop exactly when you see average machines with 3-4 gigs of memory. Not before.

      Let me give you a fact: You needed 64 bits the day you began to address more than 4GB of HD or otherwise needed big/precision numbers.

      Now you can prattle on about how much easier it is to write software with 64-bit processors, but it's silly. The software's written. It's too late. In fact, it takes _effort_ to port to 64-bits. So that's a non-argument.

      So cleaning up code that is pure hackery to get around 32 bit limitations is a non-argument? Unless you're offering to maintain that messy code, I think your whole reply is a "non-argument".

    3. Re:Actually, do go get that AMD or IBM chip by ProtonMotiveForce · · Score: 1

      Sorry, I meant "the need for 64-bits on the desktop is a was off".

      You don't need it. "4GB of HD"? Did you go to the "TV School of Computing"? What on earth do you mean? Virtual memory, address space?

      That was sort of my point, there, rocket surgeon. You don't need to address more than 4GB (of memory, or "HD") for _any_ desktop app. Hubris, you say? Well, I say _any_ because if you do, you need a workstation class machine and it's no longer desktop class.

      And yes, the "pure hackery" is a non-argument precisely because of the above. Most people don't yet need 64-bits of address space. If they do, there are workstation solutions (from many companies).

  73. Re:gotta compete by Waffle+Iron · · Score: 3, Informative
    The logic to convert x86 instructions to micro-ops takes up space on the die and uses extra power.

    However, the compact legacy CISC instruction set does conserve on instruction cache space. This offsets much of the cost of the conversion logic. Moreover, it allows custom optimizations for the exact architecture du jour without affecting binary compatibility.

    And any way you look at it, you have to read from memory a lot more often with 8 "general purpose" registers than 32 real GPRs, which is what most sane CPUs have.

    Many modern X86 CPUs have more than 32 real GPRs which are utilized by register renaming. Like quantum mechanics, the processor state for any given instruction is smeared out over time and space, and the CPU is operating on many instructions simultaneously. The number of visible registers just doesn't matter as much as it would seem on the surface.

    Itanium doesn't have to do this, PowerPC doesn't have to do this, no modern ISA requires this nonsense.

    They will when somebody figures out the next architecture trick that doesn't match the assumption of the designers of their ISAs. Take a look at history; remember when MIPS stood for "Microprocessor Without Interlocked Pipeline Stages"? What did the R4000 introduce? Could it be - interlocked pipeline stages? Exposing CPU implementation details to the software is not something that wears well over time.

    It doesn't just "scrape out a lead" in floating-point benchmarks, it absolutely destroys the x86 competition.

    That's because the FPU has not been very important in the X86 market up to this point. Business and multimedia apps just don't need it. If AMD or Intel put their efforts into an X86 with ultimate FPU performance, it could match or beat the Itanium.

    I suspect that Intel took advantage of the huge schedule delays in the Itanium to throw in more FPU horsepower because it had to beat the consumer-grade chips on something.

    And oh yeah, its running at what, half the clockspeed of the P4? If Itanium had the same economies of scale behind it at this point, there would be no competition.

    As I said, the cache and memory architecture is the primary factor in the performance of CPUs today. Clockspeed, instruction set, registers ... who cares? Everything that's not cache is only a small fraction of the die size.

    All of that hardware architecture stuff is a red herring. Worrying about those non-issues has caused the Itanium schedule to slip nearly a decade while they desperately tried to write a C compiler that could statically wring out performance from their brittle concurrent execution model without the benefits of the run-time statistics information available to the X86 code translators.

  74. Good point, one little problem. by Groo+Wanderer · · Score: 4, Informative

    I didn't consider timing when I wrote the story, or any of it's predecessors. Silly as I am going to the A64 launch tuesday. Anyway, I have been chasing this story since the chip-architect articles. The timing was unfortunate, but it wasn't an Intel plant, that much I can assure you.

    For about 3 months, I have known there was 64 bit functionality there, but I didn't have enough to prove it to my own satisfaction. I chased leads, interviewed people, and got that info.

    The fact that IDF brought me into close proximity with a ton of sources was the thing that got me so much info so quickly. There was only one thing from Intel directly, the rest were from third parties supporting the chip. If IDF had happened last January, I probably would have gotten the info then.

    -Charlie

    1. Re:Good point, one little problem. by theolein · · Score: 1

      You mean Intel is incapable of planning a little Astroturfing ahead of time?

    2. Re:Good point, one little problem. by Groo+Wanderer · · Score: 1

      No, I mean they didn't do so to me. They went on a 64-bit is worthless, and 100 watt CPUs are peachy tear shortly before and during IDF. I know where I got the info, and I know how those sources feel about Intel. None of those things were plants this time. The other thing is that the info ran counter to the official astroturf campaign that I was getting as a memeber of the media.

      That said, look around, read up on it, and make up your own mind. :)

      -Charlie

    3. Re:Good point, one little problem. by Shadow99_1 · · Score: 1

      Just admit it: You got Owned by the Intel FUD team...

      I won't believe Intel offering a 64-bit desktop solution til the actually do offer one... I also don't beleive a bit of extra silicon that isn't completely fuctional is a good indicator to '64-bitness'. I simply don't believe the hype (at least not from anyone close to Intel).

      I mean if you really know now that it has 64-bit support then tell us oh knowledgable one, what 64-bit ISA does it use? I know it can't be EPIC as that doesn't look anything like x86 at the silicon level. I also know Intel would rather shoot itself than use x86-64 (or as AMD renamed it recently AMD64) even though they have access to it. So what marvelous new ISA does it use?

      --
      we are all invisible unless we choose otherwise
    4. Re:Good point, one little problem. by Anonymous Coward · · Score: 0
      Apparently you don't know shit about computer architecture. A couple of 64-bit functional units do not a 64-bit ISA make. That's just game console marketing crap. "Oooh, look, some random part is 64 bits wide, so it's a 64-bit system!" The thoroughly 32-bit Pentium-branded chips have had 64-bit data busses and 64-bit FPUs since the beginning, and 64-bit "MMX" units since about 1996. There's "64 bit functionality" all over the place, nothing new there.

      It's not 64-bit until it has 64-bit GPRs and 64-bit flat virtual addresses, as in the AMD x86-64 chips. Get a clue, tabloid boy.

  75. amd64 CPU's available _now_ by Brian+Ristuccia · · Score: 4, Informative

    You can order amd64 systems from places like appro and Penguin Computing right now, with decent sized collections of 64-bit applications provided by popular distributions such as SuSE. Let's not forget that the amd64 CPU's can run ia32 binaries at speeds faster than many ia32 CPU's and on a system with an amd64 kernel allow for more aggregate address space consumption across processes and the ability to install tremendous amounts of physical memory for buffers and cache even if individual processes can only take advantage of a few gigabytes.

    With other groups like the Debian project well underway in their amd64 porting efforts, you can expect thousands of popular applications built for the amd64 platform. There's tons of software available for amd64 already, and you can bet by the time that AMD releases their "Athlon64" or whatever they're targeting the low-end market with, there will be even more.

    1. Re:amd64 CPU's available _now_ by Slack3r78 · · Score: 1

      I agree with you totally on the virtues of AMD64, but there WILL be a lag time between the release of the Athlon64 and native software. Official release date of the A64 is this Tues, Sept 23 (my birthday - works out nicely :) ). Windows XP for AMD64 is slated for sometime after the first of the year, so I honestly wouldn't expect much in the line of native software before then.

    2. Re:amd64 CPU's available _now_ by IM6100 · · Score: 1

      And the 64 bit world can only get better with actual, real emphasis, i.e. the 'credentials' that for some reason x86 architectures push.

      Why, my Sparc Ultra 1's, which are 64 bit, and which I bought at auction about a month ago for $12.50 each, have a growing body of apps 'fixed' to run on them, with NetBSD/Sparc64. Of course, 64 bits on Sun hardware is very, very 20th century.

      --
      A Good Intro to NetBS
    3. Re:amd64 CPU's available _now_ by Anonymous Coward · · Score: 0

      Debian? Wow! You'll be able to run "mutt" in 64-bit mode! Mission accomplished!

      Just joking there. A large group of the people who are really interested in commodity 64-bit computing are RDBMS users. So, the big missing applications are Oracle, SQL Server, and DB2. And a native JVM. And various ERP systems.

      Anyway, it will take a little while for Opteron to get there.

    4. Re:amd64 CPU's available _now_ by skyhawker · · Score: 1

      Don't Oracle and Java already run as 64-bit apps on UltraSPARC? And it seems to me that Sun has been producing some fairly decent "commodity" 64-bit workstations for a while, and they're getting better. I run Debian on one of my AlphaPC's, but I will admit that the only RDBMS that I run on it is PostgreSQL. I'm not sure what's available for Tru64 Unix, but I wouldn't be surprised if both Java and Oracle run on that as 64-bit apps.

      --

      The best diplomat I know is a fully activated phaser bank.
      -- Scotty.
    5. Re:amd64 CPU's available _now_ by ProtonMotiveForce · · Score: 1

      Right... I mean, so many people out there are hitting that pesky 3/4GB limitation in their day-day computing lives.

      64-bits is the domain of workstations and servers, it has no point in low and mid-end computing.

    6. Re:amd64 CPU's available _now_ by Anonymous Coward · · Score: 0

      You may have noticed that we are talking about Opteron - not UltraSparc or Alpha. Commercial application support depends on a lot of other things other than the code portability.

    7. Re:amd64 CPU's available _now_ by bhtooefr · · Score: 1

      Yeah, and Bill Gates said that in 1981, except the number was 640KB. Trust me, MS WILL find a way to suck over 4GB with Windows Blackcomb or something. That's why I'm using 2000, and when it gets too outdated, I'm jumping the MS ship.

    8. Re:amd64 CPU's available _now_ by jesco · · Score: 1

      "64-bits is the domain of workstations and servers, it has no point in low and mid-end computing."

      For now. A few years ago, I was happy to have 16 MB RAM in my computer; now I have 16 times that much RAM and couldn't possibly think of doing anything with only 16 MB.

    9. Re:amd64 CPU's available _now_ by ProtonMotiveForce · · Score: 1

      For now, and for the next 5 years. People love to drag out that whole 640K quote.

      PersonA: We won't need 32 processor systems on the desktop for a long time.
      PersonB: Ahaha. Fool! And we won't need more than 640K of memory, right? Ahahaha.

      Uhh, yeah...

    10. Re:amd64 CPU's available _now_ by Anonymous Coward · · Score: 0

      You are a retard who doesn't belong on the Internet. Go kill yourself. Your only life revolves around your own death. The end.

    11. Re:amd64 CPU's available _now_ by thisgooroo · · Score: 1

      but you can assme that if something runs on another 64 bit machine, it's 64 bit clean, so the porting effort to the opteron wouldn't be all that bad (not much more than a recompilation)

  76. Re:It would almost have to follow AMD's convention by Anonymous Coward · · Score: 0

    I'm sure Intel would love to have an incompatible instruction set. However the real question is if Microsoft will let them get away with it now that MS is already supporting both AMD64 and IA64. Fact is that Windows availability is make-or-break for any mainstream CPU.

  77. Re:Attention Colonials. by Anonymous Coward · · Score: 0

    feh

  78. Intel is an AMD64 licensee by charnov · · Score: 2, Interesting

    Intel has access to the AMD64 ISA from AMD as part of their cross-licensing deal years ago. The big thing is that if Intel comes out with ANOTHER 64 bit ISA, then all of their Itanium customers (and co-developer HP) who have invested billions in the Itanium will be very angry.

    My bet is that Intel won't go anywhere near 64bit on the desktop for a very long time (like never). We will see dual (or more) cores before that ever happens (which is slated for '05).

    --
    [RIAA] says its concern is artists. That's true, in just the sense that a cattle rancher is concerned about its cattle.
  79. Re:gotta compete by Anonymous Coward · · Score: 0

    As I said, the cache and memory architecture is the primary factor in the performance of CPUs today. Clockspeed, instruction set, registers ... who cares? Everything that's not cache is only a small fraction of the die size.

    Then surely it would be fair to compare the Itanium 2 to P4 and Athlon chips running at the same clock speed, since it doesn't matter. In that case the x86 chips are clobbered in ALL areas. For that matter even the IBM PPC 970 (which has less cache and a much smaller die) wins in that competition. Clock speed is the ONLY thing keeping current x86 CPUs in competition. If there was an Itanium 2 or Power4 CPU running at the same clockspeed as a P4, with the same amount of cache, the x86 chip would not be able to compete.

    All of that hardware architecture stuff is a red herring. Worrying about those non-issues has caused the Itanium schedule to slip nearly a decade while they desperately tried to write a C compiler that could statically wring out performance from their brittle concurrent execution model without the benefits of the run-time statistics information available to the X86 code translators.

    And now it has allowed Intel to build, beyond dispute, the fastest general-purpose CPU on the market today. And if it weren't for the paralysis of the mainstream PC market, it might be possible for a consumer version to be rolled out in an orderly manner in the next decade to the benefit of everyone.

  80. Nope by Groo+Wanderer · · Score: 1

    I posted a bit about this above, but no, it is not their doing. They are going to be very very cross with me for this. I am expecting Magee to get a nasty letter from Intel PR about me. Luckily, he is in Taiwan this week, and will probably lose it in the shuffle :).

    -Charlie

  81. Re:I wouldn't buy the Athlon anyway by Anonymous Coward · · Score: 0

    Dude, KT133A sucked.

  82. Re:I wouldn't buy the Athlon anyway by WoTG · · Score: 1

    Well said.

    I suspect that AMD systems had more problems proportionally than Intel boxes, but the reason was that since AMD chips (and Cyrix for that matter) were cheaper, they tended to get bundled with other cheaper components. Flakey motherboards, undersized power supplies, off-brand hard drives, generic ram all provide plenty of opportunity for unstable systems. Unfortunately, it was AMD that would always get the blame.

    Hopefully that negative image will go away soon - maybe having a few of the fastest super computers on the planet running AMD Opertons will smooth over the image problem.

  83. "Don't run out and buy an Athlon 64 just yet..." by colins · · Score: 4, Insightful


    I'm afraid this line of reasoning just doesn't cut it.

    Intel does not want a 64bit x86 on the market. They want to lead everyone to Itanium where they don't have those pesky AMD guys competing with them.

    It's for this precise reason that everyone SHOULD run out and buy an Athlon64. If nobody buys them, Intel will have no reason to jump into the 64bit x86 market at all.

    I for one can't wait for Athlon 64 to hit the market... I need a viable 64bit Linux workstation solution and I need it yesterday.

    -cjs

  84. Re:It would almost have to follow AMD's convention by Anonymous Coward · · Score: 0

    The beauty of this solution is that all Microsoft would have to do to recompile for the "new" Intel x86-64 architecture is change the op codes in their current AMD x86-64 assembler. The architecture wouldn't really be different, it would just be changed slightly to break exactly compatibility.

  85. Re:I wouldn't buy the Athlon anyway by Sj0 · · Score: 2, Informative

    I'd like to inform you that any modern processor in a laptop will run hot. If you don't believe that to be the case, I invite you to run a p3 or p4 laptop on your lap for several hours.

    Tell me, Amsterdam Vallon, what broke on your AMD college computer? Unless it was a defect with the construction of an AMD processor, your point will prove irrelevant. I'm using an AMD processor right now, and my Windows 2000 machine got a virus thanks to IE and broke. That's not AMDs fault. My old motherboard needed a flash upgrade to use an XP 1800+. That's not AMDs fault. My hard drive was an old 1Gb and after years of service, died. That's not AMDs fault. Furthermore, if you managed to crush your core, or if you installed inadequate cooling or did a substandard installation initially in any way, you cannot blame AMD. They make processors. Installing a P4 with some sub-par Aladin chipset motherboard by PC-CHIPS, a 100 watt power supply, an IBM DeathStar hard drive, cheap ram made in some communist country and a Socket 7 heatsink will result in your machine breaking as well.

    For the record, I'm on my fourth Athlon. I've used the chips without problems, upgraded without a hitch, and run the new chip without problems until I decided to upgrade again. My next machine is undoubtedly going to be an Athlon 64 as a result of the quality I've witnessed.

    --
    It's been a long time.
  86. 16bit? by Lispy · · Score: 2, Funny

    Yes, that sounds sweet. But honestly I must admit that this Amiga 1200 on my desk looks sweet and it runs lunix just fine. I guess those 8bit days are over. Future IS now.

    1. Re:16bit? by IM6100 · · Score: 1

      Well, NetBSD on my Mac SE/30 is cool, and all. But X11 is kinda limited on a one bit 512x342 screen. And it's really slow. It's a great machine for GNU Chess, though. And Lynx rulez.

      --
      A Good Intro to NetBS
    2. Re:16bit? by glyph42 · · Score: 1

      Isn't your Amiga 32-bit? All of mine were.

      --
      Music speeds up when you yawn, but does not change pitch.
    3. Re:16bit? by iantri · · Score: 1

      Just in case anyone is wondering.. I think Lispy means Linux but there actually is a Lunix for the C64/128.

    4. Re:16bit? by MegaHamsterX · · Score: 1

      And if you have the gvp trap door accelerator in it, the 1200 would become an easy bake oven. Imagine the Amiga was already ahead of it's time in 1993....

    5. Re:16bit? by Anonymous Coward · · Score: 0

      MC68000 has 32-bit internal registers, a 16-bit data bus, and 24-bit address bus. Call it what you will.

    6. Re:16bit? by Lispy · · Score: 1

      Must have been my subconcious again. I wrote lunix intentionelly but wasn't sure why, thought it looked cool. I guess something in the back of my mind remembered the real lunix. Funny.

  87. No by Zebra_X · · Score: 1

    From the inquirer: "So the burning question is, will Intel officially tell the world about the 64-bit extensions, and gut the chances of Itanium taking off, or will they sit on it? "

    Yes of course - the Itanic is and will always be a highend server workstation chip. It wasn't designed as consumer chip. So there is no conflict in interest with intel releasing a 64 bit Prescott. In fact, the product offering from intel and AMD line up quite nicely: Opteron vs. Itanic and Prescott vs. Athlon64.

    Instead of touting a 64 bit capability with out a software platform to harness the power of the 64 bit processor it's not really a compelling product feature. Intel will wait or announce very close to when MS ships 64 bit XP. Intel will be able to point to their processor, and a mass market OS that the consumer will clearly identify as benefiting from the extra power. That way - they don't waste money by producing or marketing a product that doesn't have a clear advantage/use over the current modus operedi.

    1. Re:No by Anonymous Coward · · Score: 0
      Of course their original plan was for Itanium to replace everything. That's the whole point -- to create a new kind of architecture that not only is faster than anything else out there (didn't quite work out but they're working on it), but more importantly is protected by patents that prevent AMD from competing (intel made it here, except for the small problem called x86-64). The official line for now is "itanium is only for servers" but then again, that's always been the official line for new and improved intel processors.


      At the moment they are doing fine with their x86 offerings, there is no pressing need for the desktop market to adopt 64-bit solutions, and intel needs to get back the billions of dollars they spent on Itanium development. So they sell Itanium for big bucks, only for servers, and sell x86 on the desktop market. But don't think for a moment that they wouldn't like to move everyone over to Itanium as soon as they can.

  88. Re:gotta compete by Waffle+Iron · · Score: 3, Interesting
    Clock speed is the ONLY thing keeping current x86 CPUs in competition. If there was an Itanium 2 or Power4 CPU running at the same clockspeed as a P4, with the same amount of cache, the x86 chip would not be able to compete.

    And why isn't there an Itanium 2 or Power4 running at the same clockspeed as the P4? It's because they can't. To do more work per clock, they use more logic, and that takes more time. Don't you think that Intel would have a 3.2 GHz Itanium on the market now if it were technically feasible?

    All of these CPUs use similar fabrication technology. This technology is capable of a certain number of fundamental logic operations per second per square millimeter. The P4 uses high clockspeeds only because it is marketed to users who think that MHz==performance. If marketing requirements were different, the P4 would have been designed to get the same performance out of 1/10th the clock speed with the same die size and the same manufacturing cost.

  89. this is a (supposed) underdog competition by mbreitba · · Score: 3, Insightful

    The AMD vs Intel war has been going on since the 386 days. When you bought a 386 or 486, you probably had an equal chance of getting AMD or Intel, and you didn't even know it. AMD won the war in the 486 market, remember the DX4120 or DX4133? Those were AMD chips. Intel just has a better marketing machine. Intel Inside(r) came around in the late 486 and Pentium days. AMD nor Intel will win or lose in this battle. The only people that will come out ahead will be the consumer. I just can't wait till the price cuts come around.

    1. Re:this is a (supposed) underdog competition by IM6100 · · Score: 1

      Nobody remembers the DX4-120, because everybody was getting into the Pentium about then. There is a whole class of second-source abominations that you fail to mention that put a bad, bad sheen on non-Intel parts in that era. All those Cyrix '486' parts that plugged into a 386 socket... and later, all the AMD '586' parts that plugged into a 486 socket. It all looked, and in some ways still looks, like a sad but stupid story of a dog addicted to tailpipe fumes.

      Just my observations.

      --
      A Good Intro to NetBS
  90. Re:gotta compete by Anonymous Coward · · Score: 1, Informative

    To be more accurate, Intel didn't do it first, but rather the NexGen 5x86 did it first. AMD bought NexGen, in part b/c their K5 sucked ass. and it was the NexGen engineers (in part at least) who made the K6 as well.
    So, it wasn't just 6th gen processors that had RISC emulating CISC.
    --
    tabris

  91. Of course by cubicledrone · · Score: 1

    Don't run out and buy an Athlon 64 just yet...

    Yes. Be sure to give first right of refusal on all CPU purchases to the Pentium.

    And don't even think about the G5...

    --
    Business isn't willing to pay for products, innovation and careers, so we get brands, mortgage commercials and layoffs.
  92. Compiler by vlad_petric · · Score: 2, Informative
    To be more specific, the compiler has to build traces (or hypertraces) from multiple basic blocks, as the level of paralellism in a basic block is just too small (this is also called "Flynn's bottleneck"). To do this properly you need profiling. JITs and software interpreters can do this on the fly (i.e. you don't need 2-steps compilation), and that's the reason software emulation does better than the hardware one (note: VLIW-scheduling in hardware is possible, but no processor does this AFAIK)

    I also agree with you about RSE being a mess - but stackable registers (similar to register windows in Solaris) is a very effective mechanism for reducing memory accesses. It does make out-of-order execution a living hell, but in the end it all comes down to stressing the memory less, as RAM doesn't follow Moore's curve ...

    --

    The Raven

    1. Re:Compiler by thisgooroo · · Score: 1
      but stackable registers (similar to register windows in Solaris)

      register windows increase the work that must be done on context switches and have less flexibility than interprocedural register allocation

  93. Risc .. by Anonymous Coward · · Score: 0

    Maybe they just took a PowerPC II chip and installed AIX 4.3.3 on it and turned on the 64bit kernel extensions...

  94. x86 has been 48-bit for years by Animats · · Score: 2, Informative

    x86 machines have had 48-bit address spaces for years. Some of them even bring out a few more pins, so you can address more than 4GB of memory. It's even supported by both Linux and Windows. You can't have more than 4GB per process space, but you can have more than 4GB in the machine. Works fine.

    1. Re:x86 has been 48-bit for years by cant_get_a_good_nick · · Score: 1

      It's actually 36 bits, which allows you to address up to 64Gb of physical RAM. IIRC, it came in pentium-pro, pentium II days. It's called PAE, physical address extensions. Linux 2.4 allows you to address the extra memory. Linux 2.6 goes further and moves the kernel out of the userspace VM to it's own VM, and this allows userspace procs to use nearly the full 4Gb for themselves, and the redhat enterprise kernel for AS 3.0 backported it to 2.4. The upcoming FreeBSD 4.9 includes PAE support.

  95. Re:"Don't run out and buy an Athlon 64 just yet... by Manic+Ken · · Score: 1

    This is the oldest trick in the book. I bet that the Intel execs are dancing in the moonlight right now. Headline on slashdot: dont buy an A-64, Intel may give you a better deal if You wait...

    I usually like reading The Inquirer(esp the ranting about HP) and I sure hope this will turn out to be a true story (not that I care about Intel).

  96. 64bit isn't a panacea... by perlchild · · Score: 2, Insightful

    Just how Intel saying "We're also a little bit 64bit" change the equation? Last I checked, the greatest benefits to 64 bits were twofold 1) possibility to interlayer multiple instructions 2) Faster memory throughput Now Intel, with hyperthreading, has been saying until Prescott "Hyperthreading gives you the multiple instructions goodness of RISC, without the cost" With Prescott around: "Now with the multiple intruction goodness of RISC" Intellectual honesty is dead, marketing is dancing on it's grace As for 2) Intel won't give you that(and a sizeable cache to do something useful with it) unless you buy a "server" chip, for several hundreds of dollars more. It's called good business practice... (Charge what people are willing to pay...) And guess what, people who buy servers are willing to pay more for high-throughput, because they need it to make money... Apologies for the oversimplifications, and for anyone who might posted similar ideas earlier... Intel's been saying they were better than everyone else, until they lose enough money to have to lay off their entire PR department/outsourcer, they'll never really try to prove it...

  97. # of GPRs by vlad_petric · · Score: 1
    You're clearly right about instructions requiring operands to be in some registers, etc. The compiler (IIRC) usually keeps EAX through EDX for such computations and register-allocates SI, DI and BP (if available). You clearly have to move stuff back and forth between EAX->EDX and these 3 registers, but a register copy is extremely cheap these days.

    It's probably wrong to call them general purpose registers (although that's what Intel does), but the compiler can make use of them for integer operations.

    --

    The Raven

    1. Re:# of GPRs by Anonymous Coward · · Score: 0

      They are general purpose registers. that term was used before the use of compliers exploded and assembly was the language of choice (or more accurately the lack there of). they are called general purpose register because programmers are not restricted to using them for a specific task. for example eax, ebx, si, di ... etc can be used for storing any kind of data and do various type of operations (though there are slight usage restrictions involved based on whether or not the register can act as a pointer). other register like the stack pointer, base pointer, instruction pointer, ds, ... etc had a specific purpose.

  98. More like... by StandardCell · · Score: 1

    A super-precision 32-bit carry/overflow.

  99. Who is she?!? by toeofdestiny · · Score: 0, Offtopic

    To the right of the article! She's beautiful! :-) http://www.theinquirer.net/images/ads/Inquirer/ali _lass.jpg Alternate Text: "Stranded INQ hack Paul Hales snapped this employee of ALI at the Intel Developer Forum" Uh?

    1. Re:Who is she?!? by Groo+Wanderer · · Score: 1

      She is the 'Marketing Communication Manager' for ALi Microelectronics. No offense, but I am not going to put her name and number here :). What stuns me about the whole affair is that Hales labeled the pic right AND alt tagged it. I am shocked, and he must be much more bored than he tells me.

      -Charlie

  100. Re:I wouldn't buy the Athlon anyway by GarfBond · · Score: 3, Insightful

    It's why they don't call them laptops anymore. Look on any major computer manufacturer webpage, you'd be hardpressed to find the word "laptop"

    Dell - Notebook
    HPAQ - Notebook
    Alienware - mobile gaming
    VoodooPC- mobile

    They don't call em laptops anymore because, as you've noticed, they often don't work well in your lap

  101. Re:I wouldn't buy the Athlon anyway by Anonymous Coward · · Score: 0

    Yeah, here's another me too.

    AMD K6-2/333 mHz was my first AMD chip. Lil sucker still runs flawlessly in my server. Been running 24/7 for several years now. No issues whatsoever.

    Athlon 600 (One of the originals - the slot types) was next. Damned fine performance, kicked the living shit out of any Intel offering at the time.

    Retired that for an Athlon XP 1800+. Runs brilliantly, and quite frankly, I doubt I'll need to upgrade for another two years, unless the 64-bit world really takes off.

    I've also got a 1 GHz Duron in my laptop. Runs hot? Sure. But my lap hasn't been burnt. Can't say the same for friends who have bought Intel-based laptops. (Though, in all fairness, I'd rather have a Powerbook.. Too pricey, though. ;))

  102. Re:It would almost have to follow AMD's convention by Anonymous Coward · · Score: 0

    Microsoft != Linus Torvolds. There's a whole bunch of testing, marketing, and distribution overhead they'd have to maintain for a new arch. Not that they couldn't afford it.

  103. Re:I wouldn't buy the Athlon anyway by CowBovNeal · · Score: 2, Insightful

    Jeez man. I am at a loss for words! You work on the tech section of the wsj and you are so tech illiterate?
    Which websites do you frequent? nerve.com, disgruntledhousewife.com ? cosmpolitan?

    Maybe you should frequent some hardcore tech sites before you troll.
    AMD is more value for money and a better perfomer than the Intel processor.

    "My current AMD is way too hot and my laptop burns my lap". Unless you have a ultra low voltage Pentium 3 even the normal Pentium 4 and Pentium 4 mobile will leave you sterile.
    On hindsight, maybe that's a good idea.

    "Oh, and my college computer was an AMD too, and broke several times."

    Ok, even more proof that you are fscking clueless about technology. God only knows hows you got employment in the tech section of the wsj.

    If the AMD processor was the problem, you would only have to replace the processor ONCE.
    I've dealt with about 15 AMD processors in the pas 3 years and once the processor went bad( a friend's). Got a free replacement due to the 3 year warranty and everything was rolling again.
    If your computer breaks repeatedly, the problem is fscking somehwhere ELSE!
    Why blame the processor?
    You might have used a el cheapo heatsink, maybe the ram was bad, the motherboard....
    The best reason I can think of is maybe YOU messed up something.

    Maybe I should use my subscription and let the editors at wsj know what a tech illiterate person they've employed.

    --
    Bush is on fire and its not good for my lungs.
  104. Re:Attention Colonials. by lewp · · Score: 1

    What the fuck is Britain?

    --
    Game... blouses.
  105. Re:I wouldn't buy the Athlon anyway by danielsfca2 · · Score: 1

    I never had a problem with mine.

  106. THAT'S THE UNDERSTATEMENT OF THE YEAR by pr0ntab · · Score: 1

    Christ. If you look at power usage, and speed, and the cache it requires to operate at that speed, and the overinflated cost... well, I mean, it makes me want to go buy a G5 and hope no one notices.

    Maybe I paint it pink n purple. ^_^

    I, for one, welcome our new 64-bit x86-compatible overlords.

    --
    Fuck Beta. Fuck Dice
  107. OT, but what the hell by red+floyd · · Score: 1

    Are you a mendicant?

    --
    The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
  108. Re:gotta compete by Anonymous Coward · · Score: 0

    It is important to note that actually, there was NO competition for x86 processors until after the Pentium came out. There were, of course, x86 processors made by other manufacturers. But until the Pentium/586 era, these were all made using licensed Intel designs. Intel, at the urging of IBM, had licensed the 8088 and some subsequent designs to other manufacturers because IBM wanted to ensure a stable supply. These licenses continued until the 486 era. Some manufacturers did make alterations but they were all essentially based on Intel's designs.

  109. Re:Attention Colonials. by Anonymous Coward · · Score: 0

    Yeah, because Tony Blair isn't on Bush's leash. Good luck with your delusions, let me know how it turns out, would you?

  110. Well, they are like half price! by unassimilatible · · Score: 1

    I am agnostic on platforms - a Mac-to-Intel convert. But those Athlon 64's are like $700 aren't they?

    I can't afford a G5 either, unfortunately.

    --
    Slashdot "libertarians": Small government for me, big government for those I disagree with. -1, I disagree with you
  111. Re:BAH! 286 is all you need. by IM6100 · · Score: 1

    The 286 processor was designed with multiprocessing in mind. There were proprietary '286 boxes out there that DID multitasking and took advantage of the 286 extensions. Protected mode is NOT a 386 innovation, it's a '286 thing. The thing that the 286 lacks that the 386 has is 'virtual 86 mode' which translates 'more better old 8086 so you can run multiple instances of the same old 8086 code.'

    Microsoft didn't do a lot with the 286, and the clone marketers just called it 'a better, faster 8088 with a wider address bus' and everybody continued to run DOS on their 286's. That's not Intel's fault.

    --
    A Good Intro to NetBS
  112. Re:BAH! 286 is all you need. by IM6100 · · Score: 1

    typo in above. 'the 286 was designed with multitasking in mind'

    --
    A Good Intro to NetBS
  113. Re:I wouldn't buy the Athlon anyway by Sj0 · · Score: 1

    I think you should double check before you do anything TOO drastic. I'm not convinced this guys credentials are to be taken to seriously.

    First, He's an Assistant Editor. Now, combine the fact that he's talking allegedly about an Athlon here(for his college computer). Assuming this, it's not hard to say that it's only been 5 years or so since he's been in school tops, assuming he bought this computer in his final year. Since Athlons don't grow on trees(Except in Ontario, but that's just pollution), it's safe to say he started college with an athlon, rather than buying it later while trying to pay off his student loans. Here's the tricky part: Since it's obvious he doesn't have the slightest bit of technical training, he almost certainly didn't take vocational training in college(which would mean, since he works at the wsj, he most likely took either a writing or arts program. That's four years right there). I'd wager he more than likely is only a year or two out of college. The fact that he felt the need to mention his job in the post(I know there are quite a few slashdot readers who are actual staff writers at places that would impress tech guys a hell of a lot more than wsj) says to me that he's fresh out of college as well, and that he's only been at his current job for a very short time. It might even be one of his first jobs too. Most people aren't too keen to announce their job as an assistant editor to a room of strangers unless they haven't really had any good jobs before or something of the sort.

    This information, paired with the fact that his e-mail address listed is a yahoo account, rather than either a wsj account(Which a person who was serious about his sig would undoubtedly use) or even an ISP mail account, lead me to believe this guy is an intern(perhaps under some other name, but an intern is an intern).

    My advice, if I am correct about his status, is not to bother talking to the wsj. Speaking from experience, most places tend to ignore critisism about new interns. :)

    --
    It's been a long time.
  114. Re:I wouldn't buy the Athlon anyway by DraconPern · · Score: 1

    I am all for AMD processors, but I have yet to see an AMD laptop that doesn't freeze up randomly.

  115. compiler technology hasn't.... by oliverthered · · Score: 1

    Why not make a profiling Just in time compiler, after a few runs you should have almost optimal machine code.

    --
    thank God the internet isn't a human right.
  116. Re:"Don't run out and buy an Athlon 64 just yet... by gerardrj · · Score: 3, Interesting

    Then why, precisely, are you here chatting about Intel and AMD 64 bit chips when GNU/Linux has been running on 64bit DEC Alphas for over 5 years, And YellowDog Linux runs very nicely on the G5?

    --
    Article X: The powers not delegated... by the Constitution...are reserved...to the people
  117. I don't like political correctness by unassimilatible · · Score: 1

    But I also don't believe that politeness - or common sense - permits one to say things that will get your arse kicked in if you said it to another's face.

    --
    Slashdot "libertarians": Small government for me, big government for those I disagree with. -1, I disagree with you
    1. Re:I don't like political correctness by scott_evil · · Score: 1

      Yet the fact that it's so over the top doesn't make it funny to you? I certainly had a chuckle or two as I read it.
      Stereotypes are funny.

  118. Itanium? by TheLink · · Score: 2, Insightful

    Thing is, if I wanted an expensive non-x86 64 bit platform that outperforms x86 platforms, why not IBM Power4 stuff? Why not some other existing tried and tested 64 bit platform? They've been out for years already. There are TONS of alternatives, and in those areas performance is often not that dependent on CPU either, nor the main thing.

    Itanium is a late-comer to the nonx86 64 bit club (PowerPC, Power, SPARC, SPARC compats (PRIMEPOWER), MIPS, Alpha).

    I can see why one would pick Opteron over the others even if it doesn't perform quite as well. Just for the 32 bit x86 compatibility and performance.

    If you go back in time it's like asking someone back then to switch from Intel 386/486 to Intel 88000. Why not Alpha, Motorola 680x0, SPARC etc then? If you're going to do that sort of thing then I sure hope Intel is making it extremely worth it.

    --
    1. Re:Itanium? by DarkEdgeX · · Score: 2, Insightful

      Itanium is a late-comer to the server 64-bit market. Itanium is NOT a late-comer to the 64-bit desktop 64-bit market. In the latter case, AMD is the late-comer.

      Given the architectural advances inherent in the Itanium's design, I sincerely hope it wins out in the desktop arena when that battle is played out. With AMD releasing their x86-64 CPU's, I imagine this battle will become much more center stage, and maybe we'll see the Itanium (or a desktop variant) seeing some huge price drops sooner rather than later.

      IIRC, Microsoft already has versions of Windows that will run on IA-64 hardware, so that just leaves the other killer apps mentioned before to target IA-64 natively to make it a more desirable platform.

      --
      All I know about Bush is I had a good job when Clinton was president.
    2. Re:Itanium? by Anonymous Coward · · Score: 1, Informative

      88000 was a Motorola RISC processor from the late 1980's. Perhaps you mean Intel i860? (Intel's late 1980's RISC processor.)

    3. Re:Itanium? by bhtooefr · · Score: 1

      Ah, the one that delayed Microsoft's backstabbing of IBM...

      If you don't know the background story, MS was developing NT (just NT at the time, and it stood for the CPUs nickname) for the i860 on 386 PCs with emulators. If the i860 were out, Windows NT would have killed OS/2 MUCH earlier (or still have been named NT, and become OS/2 2.0). However, they had to go to a MIPS CPU, and then port to the i386, which delayed Windows NT (it WAS at the time Windows NT).

    4. Re:Itanium? by Joe+U · · Score: 1

      While Microsoft was developing Windows NT, they decided on a modular system, with support for the N-10 processor, x86, MIPS, Alpha and eventually PPC. When launched, Windows NT suppored x86, MIPS and Alpha.

      There was no chance of Windows NT becoming OS/2 2.0, since it was not developed with or blessed by IBM. That and OS/2 2.0 was already complete.

    5. Re:Itanium? by Mr.+Frilly · · Score: 1

      Whether or not the Itanium's 'design is an "architectural advance" remains yet to be seen.

      For sure, it's elegant on paper, but consider this: Knowing the number of years and amount of money that Intel's thrown at this thing, why is it's performance only on par with other existing 64 bit chips?

      And that's of course if you believe the spectint/spectfp scores that intel publishes will translate to real world performance. Itanium performance is much more application dependent then more conventional chips.

    6. Re:Itanium? by DarkEdgeX · · Score: 1

      The design of the IA-64 architecture is such that it scales well with larger and larger die space. It's designed to be able to execute code in parallel, in fact, that's the cornerstone of the way it encodes instructions (in bundles, with multiple bundles possible to be executed at once if the CPU supports it). IIRC the original Itanium and Itanium 2 don't really exploit this yet, but rest assured, it's something that will make the IA-64 architecture outperform current and future revs of other 64-bit CPU's.

      Not to mention the other architectural advances-- which aren't really ingenious, beyond the fact that more CPU registers (for example) saves memory bandwidth, and so on. A lot of the features IA-64 boasts are just logical extensions to IA-32, but some of it is particularly cool since it's very forward looking (the instruction bundles) and will scale well.

      --
      All I know about Bush is I had a good job when Clinton was president.
    7. Re:Itanium? by jonadab · · Score: 1

      > Itanium is NOT a late-comer to the 64-bit desktop 64-bit market.

      You did say desktop, right? Then, you're right, as near as I can
      determine: Itanium isn't a latecomer; it's a no-show. Unfortunately,
      thus far so is x86-64; everything I've seen so far is rackmount stuff.
      I'm hoping this will change soon; when I buy my next desktop, I'm
      going to want one that can handle more than 4GB of RAM, but I won't
      be ready to give up extant applications.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    8. Re:Itanium? by DarkEdgeX · · Score: 1
      You did say desktop, right? Then, you're right, as near as I can
      determine: Itanium isn't a latecomer; it's a no-show
      It's out there and available if you want it. Microsoft already offers up a version of Windows that will run on an IA-64 based CPU. SDK's and DDK's already are available that target IA-64. The software and hardware is here today.
      --
      All I know about Bush is I had a good job when Clinton was president.
    9. Re:Itanium? by HuguesT · · Score: 1

      One word: vaporware. Maybe it will be fast, maybe not.

      For the moment, notice how Intel does not publicize the integer performance of the Itanium2 very well. It's because it is not very good. Sure the FP is good, but that's not enough.

    10. Re:Itanium? by Mr.+Frilly · · Score: 1

      Okay... So it'll be good for parallel code at some point... Sadly, most code we care about needs to be executed serially.

      But say we have code that can be parallelized. And we have all this die space... Why don't we just put more then one standard core on the same die? Oh wait, that's what IBM/Sun/etc. are already doing...

    11. Re:Itanium? by aminorex · · Score: 1

      Itanium was vapor for *years* after I got my
      first Sparc-9 64-bit desktop box. Heck, it's
      still vapor. What did Dell ship last quarter?
      About 800 Itanium servers? Woo-hoo! With
      economies of scale like that, who needs mainframes?

      --
      -I like my women like I like my tea: green-
    12. Re:Itanium? by aminorex · · Score: 1

      Its also what makes it sheer hell to write a
      compiler for the thing. With a hand-rolled
      (or should I say *unrolled*) mult-add loop,
      you can crank out mondo flops in BLAS, but
      when you try to run a spreadsheet or a non-linear
      program, you see the pathetic weakness of the
      compilers start to set in.

      --
      -I like my women like I like my tea: green-
    13. Re:Itanium? by yerricde · · Score: 1

      Sadly, most code we care about needs to be executed serially.

      Think anything with big for loops. Think signal processing. GIMP and Photoshop filters could almost certainly be reengineered to use wide parallelism. Weather prediction models would benefit as well.

      Why don't we just put more then one standard core on the same die?

      Because then the Slashdot trolls wouldn't be able to make as much of a Beowulf cluster joke.

      --
      Will I retire or break 10K?
    14. Re:Itanium? by dcmeserve · · Score: 1
      The design of the IA-64 architecture is such that it scales well with larger and larger die space.

      That is, die space that's not filled with cache. The enormous amount of cache on the chip is one of the main reasons for a lot of the Itanium's performance wins.

      It's designed to be able to execute code in parallel

      As are all modern processors. They all use a "lookahead" strategy to find instructions further along in the stream that could be executed at the same time Branching causes complications, of course, but there are a lot of techniques (e.g. trace cache) for making good predictions about which way a given branch will go. The compiler can help out, too, by arranging the instruction stream so as to make the parallelizable operations more accessible.

      The Itanium technique, from what I understand, requires the compiler to do just about everything. The compiler *has* to find the available parallelism so that it can arrange the operations side-by-side in the same ultra-wide instruction. From there, the execution is relatively simple -- the processor doesn't have to worry about finding the parallelism, the compiler's figured it all out already! So that would certainly make it easy to scale to larger available die space (i.e. just throw on more execution units). But the thing is, there's a lot you can't know about how most programs are going to behave until run-time. Much of the available parallelism *has* to be determined by the processor itself.

      That's why simple techniques to add parallelism on a single die aren't so commonplace yet -- more parallelism can be gained by adding to the *intelligence* on the chip than by just throwing on more execution units, or having multiple processors on a chip, etc.

      --
      "Orthodoxy is unconsciousness" - Orwell
    15. Re:Itanium? by dcmeserve · · Score: 1
      Think anything with big for loops. Think signal processing. GIMP and Photoshop filters could almost certainly be reengineered to use wide parallelism. Weather prediction models would benefit as well.

      If those applications were important enough to get everyone to shift to a different instruction set, wouldn't everyone have gone to PowerPC by now (think Altavec)?

      --
      "Orthodoxy is unconsciousness" - Orwell
    16. Re:Itanium? by mmol_6453 · · Score: 1

      You hint at the main argument against Itanium in your argument for it.

      During the main phase of processing, the GIMP and Photoshop probably wouldn't see a major increase in performance from a two-bundle Itanium over a two-system cluster, and definately a dual-processor Athlon or Pentium 4. There simply isn't a need for the low latency that having a multithreading(Dunno if that's the proper term.) CPU provides.

      Physics and weather simulations are excellent candidates for multithreading processors, though, since things like gravitational fields affect all regions of the simulation, meaning communication is necessary between that segment and other segments. (Assuming thread division by spatial relation.)

      --
      What's this Submit thingy do?
    17. Re:Itanium? by DarkEdgeX · · Score: 1
      That is, die space that's not filled with cache. The enormous amount of cache on the chip is one of the main reasons for a lot of the Itanium's performance wins.
      Uh, yeah... IIRC, Itanium's have larger than normal L1 and L2 caches, this is true, but they also have huge L3 caches which aren't part of the die. I was referring to die space used for more execution units to execute more code in parallel.

      As are all modern processors.
      I'm sorry, but you're incorrect.

      IA-32 based CPU's do not execute code in parallel except for very specific instructions that don't cause contention on resources (for example, if you have an instruction stream that utilizes the same register for multiple different calculations, you will be very hard pressed to get that code to execute in parallel).

      IA-64 has provisions to truely execute code in parallel, without any special instruction sequencing or instruction selection tricks to look out for. It simply does it if you tell it to.

      The Itanium technique, from what I understand, requires the compiler to do just about everything.
      Yep, and this makes the most sense. Why figure all this stuff out at run-time with look-ahead buffers and other clumsy technologies? All of this can be determined much more accurately at compile time, because the source code available to the compiler is much more likely to have it's own hints as to what the author is trying to do than a bunch of opcodes haphazardly emitted to an executable.

      Yes it puts the onus on compiler writers to do some work in making their code generator emit quality code (looking for opportunities to take advantage of parallel processor, and so on), but that's the way technology works-- you come up with something better, but it requires effort to make it work properly. IA-64 is far superior to IA-32, and has much more opportunity for performance code generation.

      From there, the execution is relatively simple -- the processor doesn't have to worry about finding the parallelism, the compiler's figured it all out already!
      Right, so I see we agree that this is a major feature of IA-64, it's ability to concentrate on code execution rather than prediction of code paths and such. Thanks for that.

      But the thing is, there's a lot you can't know about how most programs are going to behave until run-time. Much of the available parallelism *has* to be determined by the processor itself.
      I don't think you understand code generation, that, or you're being naive. The compiler is in the best position to determine what code can execute in parallel, and how best to order the instructions to gain maximum speed from the CPU in executing that code. The CPU's task is to cache the most commonly used code, basically doing the duties a profiler would have done back in ye olde DOS days. Determine the most commonly executed code paths and keep them in the cache as long as possible

      The only difference between a profiler in the old days and this cache technique is that the profiler allowed the developer to see what code was consuming the most CPU cycles. I suppose then with a profiler for IA-64 PLUS the cacheing of code, you could potentially gain some great speedups in your usual IA-32 code if you compiled it for IA-64.

      IMNSHO, IA-64 is the future of Intel desktop CPU's, and the instruction set that they'll ultimately move forward with. It scales well, it puts the work that should be done by the compiler with the compiler, and leaves the CPU with as little to do as possible besides fetching instructions, decoding them, and executing as many of them in parallel as possible. That's all a CPU should do.
      --
      All I know about Bush is I had a good job when Clinton was president.
    18. Re:Itanium? by DarkEdgeX · · Score: 1

      Thanks for the irrelevant post. I never said it was going to make a big splash in the server market. The desktop market has NO 64-bit CPU's, and the Itanium platform (IA-64) is maturing slowly but surely, and has much more testing and development under it's belt than x86-64 has. If Intel felt threatened by x86-64, IA-64 would be their best bet, IMNSHO.

      --
      All I know about Bush is I had a good job when Clinton was president.
    19. Re:Itanium? by dcmeserve · · Score: 1
      It's rediculously late me to post a reply and expect anyone to read it, but what the heck...
      As are all modern processors.
      I'm sorry, but you're incorrect.

      IA-32 based CPU's do not ...

      Sorry, I've been living in the SPARC world too long. :)

      But the thing is, there's a lot you can't know about how most programs are going to behave until run-time. Much of the available parallelism *has* to be determined by the processor itself.
      I don't think you understand code generation, that, or you're being naive. The compiler is in the best position to determine what code can execute in parallel, and how best to order the instructions to gain maximum speed from the CPU in executing that code. ...

      True, I don't have a lot of experience with the details of compiler techniques. But I have to say, I think there's a certain amount of naivete in your statement. Can compilers really be so good at branch-prediction?

      Data-dependent branches are one of the fundamental features of computer programs. Heck, it's practically the whole point. As such, there will always be situations where the probabilities of which way a branch will go cannot be known at compile time; only run time. As such, a trace cache or some such will achieve better instruction-level parallelism than compiler predictions in many situations.

      Now, to be fair, you seem to be talking about a higher level of parallelism than simple ILP. If a compiler can eeke that out of a program, it can put the resulting parallel instruction streams side-by-side for a VLIW machine.

      But of course, if it could do that, it could also interleave such instructions for a non-vliw machine to grab out of its lookahead buffer. So the two types of machines are equal in that respect, except that when the code ends up with a lot of compiler mis-predicts on branching, the VLIW machine is screwed, whereas a trace-cache or such technique on the other machine would maintain performance, after the cache adjusts to the actual situation. And a non-vliw machine could still be capable of listening to compiler hints about which way a given branch is expected to go, if it's not in the trace cache yet. (Of course, I guess the IA-32 probably wouldn't support such communication. Don't know about AMD64.)

      IA-64 is the future of Intel desktop CPU's

      God, I hope so. AMD needs the market share! ;)

      --
      "Orthodoxy is unconsciousness" - Orwell
  119. LOL by unassimilatible · · Score: 1

    Yes, and I was also on that grassy knoll in Dallas, 1963.

    If my friends heard that I, former Mac evangelist, was accused of being an Intel employee, they'd laugh their asses off!

    I wish I worked for a Dow 30 company!

    --
    Slashdot "libertarians": Small government for me, big government for those I disagree with. -1, I disagree with you
    1. Re:LOL by babbage · · Score: 1

      :-)

      Okay, I stand corrected then. Still, the way that the story is presented still smells a lot like FUD to me, even if it wasn't intended that way. But then I guess that's yet another mark of the difference between a professionally done journalism site on one hand, and Slashdot on the other... :-)

  120. Re:gotta compete by evilviper · · Score: 1
    there has been no such thing as a "CISC processor" since the Pentium Pro came out.

    An incredibly popular urban legend. Anyone know why this has been popular for so long?
    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  121. "PRESCOTT" for heavens sake by cruachan · · Score: 1

    Jeez, I know this shouldn't matter, but in the UK calling a chip 'Prescott' is going to make your corporate sysadm cringe at the thought of having to service a 'Prescott inside' labelled box.

    John Prescott is the rather 'colourful' deputy leader of the labour party. A union man with a merchant navy background, John Prescott is known for his rather casual acquaintance with English and an style of electionaring which includes physically assaulting the voters. Probably best summed up by one political comic strip which has him as a somewhat overweight and confused rottweiller.

    What next - the Lewinsky chip?

    1. Re:"PRESCOTT" for heavens sake by mabinogi · · Score: 1

      It's a code name....the chip itself will be called Pentium, just like Katamai, Coppermine, Williamette, etc...

      Probably even still a Pentium IV.

      Intel's not throwing away years of brand recogition over a new core.

      --
      Advanced users are users too!
    2. Re:"PRESCOTT" for heavens sake by fallacy · · Score: 1

      It's rather apt then.
      They're both bloated, blow out a lot of hot air, and seemingly get their respective "companies" into trouble...

    3. Re:"PRESCOTT" for heavens sake by Shorthouse · · Score: 1

      And both, presumably, have plenty of punch...

  122. Fud, FUD FUD!!! by haggar · · Score: 2, Insightful

    Intel must be really worried. But they have a very efficient weapon, called FUD. You have certainly heard of it, it has bee used extensively by Microsoft, to undermine already existing products with rumors of an upcoming OS that will blow everybody's hat off. Remember Windows NT 5.0? That was supposed to come out in 1997 (Allchin has announced it many times - shifting the release date a few months in the future, every time).

    So, here we have Itanium that isn't doing well on the market, porting to it's 64 bit ISA is hary and which performs legacy code horribly. No, really horribly.
    And then here we have Athlon 64, which is cheaper than Itanium, requires very little porting to 64 bit code and which performs legacy code fantasticly - in fact, it's so good that you might consider and Athlon 64 just to run your legacy x86 code, 'coz it's so fast.
    So what does Intel do? Float a flaming horseshit of FUD about Prescott being somewhat 64 bit - but hey, Intel didn't say it, the source was, uh, the Inquirer, for cryin' out loud!

    Well, until someone doesn't put the Prescott under an electronic microscope and makes their conclusions based on hard facts, and concludes that, indeed, The Inquirer is right, I say FUD and double FUD from a company that is known to engage in it!

    --
    Sigged!
    1. Re:Fud, FUD FUD!!! by Zak3056 · · Score: 1

      Remember Windows NT 5.0? That was supposed to come out in 1997 (Allchin has announced it many times - shifting the release date a few months in the future, every time)

      Err... you do realize that NT5 was renamed "Windows 2000," right?

      --
      What part of "shall not be infringed" is so hard to understand?
    2. Re:Fud, FUD FUD!!! by haggar · · Score: 1

      Err... you do realize that NT5 was renamed "Windows 2000," right?

      That was the whole point of my post, Einstein.

      --
      Sigged!
    3. Re:Fud, FUD FUD!!! by Anonymous Coward · · Score: 0

      Man, you're thick.

      Mod parent down,"-1 stupid".

    4. Re:Fud, FUD FUD!!! by Zak3056 · · Score: 1

      That was the whole point of my post, Einstein.

      I was about half-sure that is what you were TRYING to say, but you said it quite poorly. Don't use the present tense to describe something that happened in the past. (i.e. "Allchin has announced it many times" implies you believe he is still doing it.)

      --
      What part of "shall not be infringed" is so hard to understand?
  123. Re:"Don't run out and buy an Athlon 64 just yet... by TheLink · · Score: 2, Interesting

    That's the thing. Those solutions (including the Itanium) aren't x86 compatible in a practical way.

    It's not such a big deal with open source software, but check out the price/performance of x86 desktop hardware and peripherals some time.

    --
  124. Stuck in the past?? by TheLink · · Score: 2, Insightful

    Stuck in the past? Holding back technology?

    Check out the price/performance of x86 some time. Also in many cases they don't even run much hotter or consume that much more power if you compare processors of similar performance.

    The larva has evolved, grown wings and it flies. It's still an ugly bug, but it flies. And to the disgust of many chip architecture academics in their ivory towers, it flies faster than many supposedly elegantly designed RISC/postRISC bugs.

    Heck, I hope the x86-64 becomes popular just to see the look on their faces. :)

    BTW, have you actually looked at the PC architecture recently? Have you actually looked at the memory bandwidth? Have you noticed that Sun and Apple have PCI slots and aren't talking much about s-bus and nubus anymore?

    Stuck in the past? Maybe you are, and you still long for the good old days when a vendor held you by your balls and said "Jump!".

    --
  125. Embarassing fact. by TheLink · · Score: 1

    If you really need a lot of fast SPARCs you have to buy Fujitsu PRIMEPOWER.

    You run Solaris on those just like you run Suns. The difference? Not sure about the price but you get hardware level instruction retry, and a modern CPU design with the expected performance that comes with it.

    --
  126. Re:It would almost have to follow AMD's convention by Anonymous Coward · · Score: 0

    Don't worry, they can handle it. They shipped NT4 for x86, Alpha, MIPS and PowerPC on a single CD. If Intel wants it enough, it will be done, and as proposed the port will be as easy as possible (with the compilation port a trivial change, with no new code required, and the core logic drivers done by Intel as they are for Intel chipsets now).

    Further, if it is successful AMD picks up the new opcodes they will be able to drop the AMD-specific version eventually.

  127. Remember HyperThreading... by brucmack · · Score: 1

    With HyperThreading, I believe all of Intel's Northwood P4 cores had HyperThreading stuff inside them, just disabled. This was meant to simplify their manufacturing, so that when they started releasing real HT processors they didn't have to make any major changes to their design.

    Perhaps they are doing the same thing here... put in rudimentary 64-bit support that might not be efficient or even work properly, so that later on if they do decide to activate it, they don't have to completely redesign their core.

  128. K6-2 - good for servers by Anonymous Coward · · Score: 0

    I am running one still in a server machine, and the point is that as long as you run integer arithmetics on it, it performs *REALLY* well. The FPU sucked, yes, but server software rarely does need the FPU a lot.

  129. Re:"Don't run out and buy an Athlon 64 just yet... by gerardrj · · Score: 3, Interesting

    Ahhh. So there's another variable... you need x86 compatibility. that's a different animal than simply needing a 64bit Linux workstation as you initially stated. I will warn you: much open source software is written with x86 in mind and had things hard-wired to that platform. Even when things compile on a 64bit system, they tend to fail in interesting and unpredictable ways. I've found that ignorance and lazyness seem to prevail in the open source movement when it comes to truely portable software.

    I don't know exactly what you mean by your last comment. I don't really know of any x86 specific hardware or peripherals except for the MBs and CPUs. Just about every other peripheral or piece of hardware will plug in to many Alphas and any recent Mac (drivers and firmware aside).
    I've used many video and network cards off-the-shelf as well as standard RAM in my Alpha and use standard "PC" memory, drives and peripherals on my 5 year old Mac.

    I have checked out x86 price/performance. It's not been enough to get me to purchase any of it. I get more real work done on my Mac per dollar than on x86 (no virus downtime, few system updates, etc), and my Alphas put out more heat per dollar than any x86 could in it's wet dreams.

    --
    Article X: The powers not delegated... by the Constitution...are reserved...to the people
  130. Re:I wouldn't buy the Athlon anyway by Anonymous Coward · · Score: 0

    My 600MHz Duron @ 880MHz on a via chipset worked perfectly for two years 24/7. Now I have a AthlonXP 1700+ t-bred @ 2400MHz running perfectly 24/7.

    Most of my friends who have upgraded in the last 3-4 years have AMD systems, with no major problems.

  131. Old Labour... by slipgun · · Score: 2, Funny

    Is Prescott 64-bit?

    Is Prescott 64 yet?

    --
    SpamNet - a spam blocker that really works
    1. Re:Old Labour... by trash+eighty · · Score: 1

      i always thought he was a 2-bit politician myself

    2. Re:Old Labour... by slipgun · · Score: 1

      I've just found it quite funny that Intel decided to code-name their Pentium 5 after a man most famed for building a bus lane on the M4...

      --
      SpamNet - a spam blocker that really works
  132. I found some prerelease pictures... by bhtooefr · · Score: 1

    ...of what I think is a 1U dual Xeon Prescott box: The heatsinks - priceless

    1. Re:I found some prerelease pictures... by Anonymous Coward · · Score: 0

      Uh... that looks like an Alpha board. Notice all the Digital-branded support chips on the system board...

    2. Re:I found some prerelease pictures... by Anonymous Coward · · Score: 0

      it looks like an alpha, note the heat sink design and digital logo's on the chips

  133. "640K of memory should be enough for anybody" by kmarius · · Score: 1

    That's an urban legend.

    "I've said some stupid things and some wrong things, but not that. No one involved in computers would ever say that a certain amount of memory is enough for all time." - Bill Gates

    1. Re:"640K of memory should be enough for anybody" by Anonymous Coward · · Score: 0

      Actually it's fact, though the "It's an urban legend!" claims are fast becoming an urban legend of their own.

      If someone said something monumentally stupid and you wanted to find out if they really did say it, would you ask the person who originally said it or the person who they said it to?

      Admittedly the original statement is taken slightly out of context but claiming that it never happened because Bill Gates said so is a bit naive.

  134. Re:gotta compete by Anonymous Coward · · Score: 0

    Itanium is good at FPU code because of the VLIW/EPIC design. x86 will never reach Itanium FPU performance in the same generation.

  135. Re:I wouldn't buy the Athlon anyway by xSauronx · · Score: 1
    an article in the inquirer and its on slashdot?

    wtf?

    --
    By and large, language is a tool for concealing the truth. -- George Carlin
  136. Solaris = register windows? by bani · · Score: 1

    Solaris? I think you mean Sparc.

    Cuz Solaris runs on x86 which most definitely does not have register windows ;)

    It's a cool architecture, but huge l1/l2 caches have dramatically reduced the justification for register windows. Not to mention that l1/l2 caches are infinitely more useful as general purpose.

    Register windows might have made sense back in FPM memory days when your typical L2 cache was 64k. But we're now pushing past 1m L2 caches... and QDR is just round the corner...

  137. Re:Wow! Not. by jph · · Score: 1

    Or you might want to wait a bit more after the Prescott release, because I heard both AMD and Intel are planning to release more chips that are even more powerful!! And quantum stuff too is years closer now than 1990... ;)

  138. well, maybe by penguin7of9 · · Score: 1

    First of all, Opteron has quite a big lead. There are Opteron-based distributions, compilers, and other tools.

    Also, merely having "64 bit instructions" isn't enough. What matters is whether the processor has 64 bit addressing, the ability to address lots of memory, etc. It may, but how well it works remains to be seen.

  139. No, DO go out and get an Athlon64 by Fefe · · Score: 1

    Intel has a history of cheating benchmarks and outright manipulation of "industry" benchmarks like Babco to make their products look good.

    Most of the lead of their products in benchmarks these days come from either a) memory bandwidth (Athlon 64 has even more bandwidth than P4) or b) SSE2 (Athlon 64 also has SSE2).

    Even if Prescott has x86-64 instructions, there is no reason to believe it will outperform an Athlon 64. In fact, current benchmarks indicate that Athlon 64 wipes the floor with everything Intel has to offer.

    It is true that the Athlon 64 is expensive. The Pentium 4 is also very expensive. AMD is trying to make some money here, before again descending into price wars with Intel. As soon as Intel slashes prices, so will AMD.

    I suggest reading the Inquirer regularly to read about Intel's Babco cheating details (the Pentium M Babco results make this very clear). I will not support cheats and sore losers like Intel with my money.

    1. Re:No, DO go out and get an Athlon64 by Comatose51 · · Score: 1

      While I admire your principle, I have to say that is not very practical. If somehow the Prescott does outperform the A64, I WILL get it, especially if it is cheaper.

      --
      EvilCON - Made Famous by /.
    2. Re:No, DO go out and get an Athlon64 by Zed2K · · Score: 1

      Do you not realize how many other kinds of chips Intel makes besides the main CPU's? Intel chips are in just about everything. So I guess you are just going to shun technology entirely? Oh well, your loss.

    3. Re:No, DO go out and get an Athlon64 by sundling · · Score: 1

      yah right, an intel chip that's better and cheaper?
      Step away from the crack pipe. :)

      That's like expecting to find a SONY that's cheaper and better than an AIWA. Until Joe User knows has even heard of AMD that will never happen.

  140. Re:Intel or AMD by Oshkoshjohn · · Score: 1

    Everyone already knows that AMD costs less and runs faster than anything WinIntel has or will ever field!

    --
    Goddamned kids! Get off my lawn!
  141. How is AMD staying alive? by Comatose51 · · Score: 1

    This is the thing I've never understood. They're a much smaller company than Intel. For most quarters they lose money. Yet, they're able to compete with Intel and throw in some good punches every now and then. How can they do this year after year? I'm always worried that one day AMD would just topple over but, thank whatever you want, it hasn't. This Athlon64 probably won't destroy Intel or anything but I hope it will give AMD some more breathing room to keep competing.

    --
    EvilCON - Made Famous by /.
  142. Re: Confusion about Paging by Glasswire · · Score: 1

    I suspect that the original poster talked about paging, he meant techniques for swaping memory (like Intel's PAE) in and out from the pure 4GB flat address space that a 32-bit cpu can address directly to a larger external pool. It's the reason why many IA32 servers ship with 8 or 16GB of RAM, when on paper, the cpu cannot address the space beyond 4GB.

    As you said (and it WAS an imformative post) "32-bit chips can be designed to access any amount of physical ram" -I think he meant something like PAE when I said 'paging'.

  143. Re:Attention Colonials. by Ella+the+Cat · · Score: 1

    Less of that toilet mouth. Prescott is British

  144. Re:I wouldn't buy the Athlon anyway by QuantumFTL · · Score: 1

    It's why they don't call them laptops anymore. Look on any major computer manufacturer webpage, you'd be hardpressed to find the word "laptop"

    Dell - Notebook
    HPAQ - Notebook
    Alienware - mobile gaming
    VoodooPC- mobile


    Not to be obnoxious, but I was curious about your claims and performed a search on google of each site to measure the number of pages containing the word "laptop".

    Dell - 20,800
    HPAQ - 6320
    Alienware - 39 ("notebook" only had 25)
    VoodooPC - 142 ("notebook" only had 62)


    Granted the number of "notebook" terms on Dell and HPAQ was significantly higher than the term "laptop", but it's not like the term was suddenly erased by marketing or something...

    My Powerbook G4 17" works just fine on my lap, as did my old iBook.

    Cheers,
    Justin

  145. Re:"Don't run out and buy an Athlon 64 just yet... by Anonymous Coward · · Score: 0

    I've found that ignorance and lazyness seem to prevail in the open source movement when it comes to truely portable software.

    I've found that ignorance and laziness seem to prevail in almost all programmers when it comes to truly portable software.

    I've also found that you are an idiot.

  146. Re:gotta compete by Anonymous Coward · · Score: 0

    While most of your points are valid, there are sound reasons why x86 FPU performance sucks, as there are fundamental flaws in its stack-based architecture (or so I hear, I couldn't tell you myself). That's why they came up with SSE2, which is apparently quite competitive. Of course, Intel didn't really do a very good job with the Pentium 4 FPU, but AMD usually includes a fairly decent unit.

    It's also a bit disingenuous to say that FPU performance isn't important on consumer hardware, since high performance hardware is generally thrown at games, which share many similarities with other high performance software like renderers and simulators (hmm, wonder why). A fast FPU has been important to gamers since Quake and the Pentium Pro.

  147. Re:I wouldn't buy the Athlon anyway by Anonymous Coward · · Score: 0

    Yes, several actually. I should probably preface this with the fact that I was never into the Intel=PC mentality that everyone else at the time was in. Actually, my first PC used an NEC V20.

    I have used AMD as my primary processor vendor since my 486DX40 which ran perfect in a VLB system and was later upgraded to a DX2-80. Over the years, I have used the K5, K6, and Athlon processors and will be chosing AMD as my 64bit solution when I decide to go that route.

    Problems that I have encountered were:

    K5 - poor FP performance.
    K6 - certain programs crashing due to program errors.
    Athlon - none. :) Actually, I've got one running with a chipset fan with a bad bearing (Abit board) that runs 24x7 with no problems.

    The only other problem that I can mention is AMD stupid naming on their XP line. That's hardly a problem.

  148. Re:I wouldn't buy the Athlon anyway by Anonymous Coward · · Score: 0

    I assume you're joking, but on the off chance that you're being serious, what exactly do you miss? The air conditioning bill? You know, running a few 60-100W light bulbs will burn up more power and spew more heat than any computer.

  149. Re:I wouldn't buy the Athlon anyway by Anonymous Coward · · Score: 0

    I never have to date, either... in fact, I never get to date.

    Oh, wait. You meant, "have (to date)."

    Bleh, now I just feel pathetic and lonely.

  150. Re:In other Video Game news... by Anonymous Coward · · Score: 0

    SNK trumped the 16 bit competition by releasing their 24 bit NeoGeo powerhouse.

    NEC releases it's 16 bit system to compete with the 16 bit Sega Genesis.

    Sega's last stand, the Dreamcast is a 128 bit super system that will change the world.

    No thanks people. I'll just stick to my PC which includes the powerful 80 bit 8087.

  151. Re:I wouldn't buy the Athlon anyway by mczak · · Score: 1

    You must confuse that with KT333. KT133A was really not that good, at least not the southbridge that came with it, for instance non-existant pci performance, problems with the ide interface (eventually bios updates fixed the data corruption issues at the cost of even worse pci performance).

  152. Without AMD... by Kjella · · Score: 1

    Without AMD though, I'm sure Intel would keep their new chips at higher price points for a bit longer and milk the power user crowd for a little more money.

    Not only that, but the increase in processing power would be matched to the complexity of the software. For all the MS-bashing, it would make good business sense for Intel not to release "fast" processors, but instead coerce people into buying as many generations of their processors as possible. Each time you'd want to upgrade your software, you'd want to upgrade your hardware.

    In fact, you see some of the same kind of "pacing" in the market now as well, but now mostly as a "fastest processor vs paper release" trade-off, since AMD and Intel will jump at eachother to claim the title, but without being accused of releasing vaporware. Still, that is far superior to the situation if Intel was completely alone in the market.

    Kjella

    --
    Live today, because you never know what tomorrow brings
  153. Hey Charlie... by Decimal · · Score: 1

    It was hard to tell from the article, but it seemed to imply that AMD's new instructions were included. Can you verify what those 64-bit instructions actually are?

    --

    Remember "Bring 'em on"? *sigh
    1. Re:Hey Charlie... by Groo+Wanderer · · Score: 1

      No, but ask me again tuesday night, I hope to know by then. Alternatively, you could just read the Inq regularly, it will show up there first.

      -Charlie

  154. Re:Nigger Owner's Manual (GPL) by Anonymous Coward · · Score: 0

    god you people need to relax. its a joke, deal with it.

  155. For home users? by yerricde · · Score: 1

    Yes, there's Windows for the platform, but what vendor sells a new IA-64 machine to end users for under $1,000? A workstation platform is generally not a "desktop" platform until it is common in homes, and it won't be in many homes until it gets below that psychological price point.

    --
    Will I retire or break 10K?
    1. Re:For home users? by DarkEdgeX · · Score: 1

      Yeah, and that's your only valid point. And I think that's all about to change since AMD appears to be trying to take on Intel in this arena. Now as to whether Prescott (with purported 64-bit extensions) or Itanium comes out as the desktop technology Intel ultimately pushes is anyones guess, but my point still stands-- Intel has 64-bit technology already out there, and it's quite likely that if Prescott's 64-bit extensions are non-existant, that they'll push Itanium's prices down to compete on the desktop.

      The thing is, Microsoft has already ported Windows to IA-64, already has compiler technology that targets IA-64 (there's a command line Visual C++ compiler included with the Windows Server 2003 DDK), and wouldn't take much effort to re-target all their bread and butter products (Office, SQL Server, etc) to IA-64 to finish the support off.

      The fact that Itanium is uber-expensive now is almost a non-issue-- the reason it's expensive is because Intel KNOWS they can charge that much because they're selling/marketing it as a "server" or "enterprise" solution, not a desktop solution. Rest assured, if it came to desktops, the price would fall and we'd see an "Itanium Xeon" with absurd pricing for the server/enterprise markets to continue feeding Intel's cash cow.

      --
      All I know about Bush is I had a good job when Clinton was president.
  156. Obvious Intel Slant by sundling · · Score: 1
    The story itself was written with an obvious Intel
    bias. That's easy to tell for several reasons:
    • They focus on the FUD: don't buy that Athlon 64
    • They point to the Intel price roadmap, inferring somehow that Intel will be cheaper
    • mention of people who thought Athlon 64s would be supreme, as if he really WANTS to say "you're wrong"

    Athlon 64 is existing technology and it's kin, the Opteron, was released back in April. So let's talk Intel x86-64 derivatives when they're on the books. It's certainly not why you shouldn't buy an Athlon 64. Go home FUDSTER. Come back when you got something with at least a launch date. Granted I read the Inquirer every day, but your article could have been more balanced.

    AMD has always provided a better value at a given performance level and will continue to do so. You can't tell me that if an Intel part has 64 bit and comparable performance that it will be less expensive. So what if a 2.8 Ghz Pentium 4 will be $178. You'll probably have
    an Athlon 64 3200+ for $150 or less at that point.

    Sounds like you're an Intel fanboy as much as I'm an AMD fanboy. If they had cards, I'd be a card carrying fanboy. :) Even if you don't like AMD, you have to admit that they're the only thing standing in the way of higher prices and slower introductions. Otherwise, we'd be talking about our new 1.6 Ghz Pentium 4 with expensive Rambus memory and how FAST it was and how cheap at only $800. I doubt Celeron would have ever existed without competition. So if AMD falls, we will ALL pay for it. Don't forget that Intel is one of those companies like Microsoft that would love to tell YOU, the customer what you can have instead of asking you what you want (like AMD). Granted AMD sometimes has their head up their butt, especially in marketing, but it's very impressive they're surviving where so many have perished. The only real competitor standing out of about 15 in x86! Via and Transmeta don't have any sort of serious presence.
  157. 24-bit vs. 32-bit addressing by yerricde · · Score: 1

    The Mac went through almost the same growing pains in the early 7.0 era. IIRC, Mac OS 7.0 and 7.1 could run in 24-bit mode or 32-bit mode, but some apps required a bit of reengineering by their authors before they could work with 32-bit mode, and in fact, some 68020-based and early 68030-based Mac models had "dirty" ROM code that didn't work with 32-bit addressing. Apple finally dropped support for "dirty" models in Mac OS 7.6, the first to require a 68030 processor and a "clean" ROM.

    --
    Will I retire or break 10K?
  158. Look at the Icons for this Article!! by sundling · · Score: 1

    To REALLY drive my point home, what is the icon for this article?? It's Intel, NOT AMD. So even in their own story, AMD finds itself in Intel's shadow, even when they are about to break into major new territory for a chip meant to be a mainstream desktop. Sure there's Opteron, G5, Alpha, UltraSparc, etc that might be used for desktop, but this will be a whole new ball game for windows. Plus this will be the first really cheap 64 bit high performance Linux machines (within 6 months when prices drop). Even now Opteron has topped the TCP price/performance benchmarks with a MULTI-processor machine beating out a dell single processor. You know multi-processor machines are generally more expensive per processor, so this is remarkable.

    I saw an application server benchmark where a dual 1.6 Ghz Opteron did almost twice as good as a dual 2.8 Ghz Xeon, which is at a little more than half the Mhz! Talk about impressive.

  159. Not even in game consoles by yerricde · · Score: 1

    IBM chose to build the PC around the x86 architecture, which pretty much dried up the market for other 16 bit processors.

    Other 16-bit processor architectures lived on in game consoles. The Sega Genesis and Atari Jaguar had a 68000 processor, and the WDC 65c816 found its way into the Super NES. Why couldn't Zilog manage to market its CPUs for use in 16-bit consoles?

    --
    Will I retire or break 10K?
    1. Re:Not even in game consoles by thisgooroo · · Score: 1
      Why couldn't Zilog manage to market its CPUs for use in 16-bit consoles?

      not sure. the best suggestion i can make: in the aftermath of the first oil crisis, several oild companies were trying to diversify. esso bought Zilog and a few other smaller companies with potential (don't ask me about the names of the other ones) and seem to have run them all into the ground. imo, Zilog didn't fail for technical reasons. I preferred the Z8000 over the 68000, and the Z80000 was a really nice design (backward compatibility without crippling the architecture

  160. The old apps by yerricde · · Score: 1

    PowerPC with Altivec does in fact find its way into scientific computing (big PPC clusters) and image editing (Macintosh computers).

    On the Windows desktop, on the other hand, these applications aren't important enough for a switch to processors with a new instruction set but which can't run the old apps in parallel on the same machine. When Apple first introduced Power Macintosh computers to replace 68K computers, Apple solved this problem by emulating legacy apps and making half the OS run in emulation until the rest could be ported. AMD's new processor will introduce hardware support for such emulation ("virtual i386" mode), making it even easier for Microsoft to port only half the OS, just as Intel did when its V86-capable 386 processor led to Windows 3.x, the first Windows version that multitasked DOS apps well.

    --
    Will I retire or break 10K?
  161. x86 has always had 64-bit instructions... by Junks+Jerzey · · Score: 1

    ...on the FPU. The Pentium FPU can not only load and store 64-bit values directly--over a 64-bit bus--but can load and store 80-bit values. In fact, all internal FPU operations are 80-bit.

  162. Wrong 64 by yerricde · · Score: 1
    --
    Will I retire or break 10K?
  163. Re:"Don't run out and buy an Athlon 64 just yet... by yerricde · · Score: 1

    I've found that ignorance and lazyness seem to prevail in the open source movement when it comes to truely portable software.

    "Ignorance and laziness"? How about finance? Most free software developers own x86 machines and don't have $3,000 to waste on a new specimen of any 64-bit workstation platform. Can you provide me with programs that emulate most popular 64-bit architectures on x86 so that I can run test suites on some other platform?

    --
    Will I retire or break 10K?
  164. Re: typical Slashdotters by pmz · · Score: 1


    Oh, I get it! I get jokes! HAHAHAHAHA...

  165. Re:BAH! 286 is all you need. by ratboy666 · · Score: 1

    I was ready to moderate, but decided to reply instead --

    Virtual 86 mode is missing from the '286 but it isn't the most important thing...

    The '286 is a 16 bit machine. This makes porting Unix software (which generally assumes a 32 bit 'int' type) a bit difficult.

    Also, the '286 does not support paging. Only segmentation. It is very difficult to get a "steady state" swapping working with variable length segments. Also, there were only 8K user and 8K system segments. Which rendered the idea of a separate segment for each data item moot.

    Also, the '286 was limited to 16MB of real memory. Which is lightweight for a GUI (fine for console based applications, though).

    Microsoft DID do a "lot" with the 286, but the user base of the time didn't see the need to play along. OS/2 1.x was actually quite choice, and exploited the '286 well.

    However, it was expensive (compared to DOS), used too much memory (not many computers had more than 640K, 2MB was considered a lot) and there weren't many compelling applications for the new protected mode. Also, OS/2 was late. VERY late.

    Doom and gloom for the 286.

    No, it wasn't "Intel's fault". But Intel just made the chips. The '286 was sampling in 1982. Personally, I like it that way. Give us the chips, and we will decide what can fly on the market and what must die...

    Ratboy.

    --
    Just another "Cubible(sic) Joe" 2 17 3061
  166. Re:"Don't run out and buy an Athlon 64 just yet... by pmz · · Score: 1

    I'm afraid this line of reasoning just doesn't cut it.

    It also sounds as if Slashdot just got astroturfed with a top-tier article. Kinda sad, IMO.

  167. Re:"Don't run out and buy an Athlon 64 just yet... by gerardrj · · Score: 1

    There's no need to emulate anything. One of the most frequent errors is assuming the size of data structures instead of querying the system for the sizes of these structures. You can do that without ever seeing a 64 bit system.

    --
    Article X: The powers not delegated... by the Constitution...are reserved...to the people
  168. Microsoft prices its operating systems per CPU by yerricde · · Score: 1

    During the main phase of processing, the GIMP and Photoshop probably wouldn't see a major increase in performance from a two-bundle Itanium over a two-system cluster

    Does even the expensive full version of Adobe Photoshop support running filters on a cluster?

    and definately a dual-processor Athlon or Pentium 4.

    Sure, it would be easy to have different CPUs do a filter on different parts of an image, but the problem here is getting an affordable WinAPI-compatible operating system to recognize the extra CPUs when Microsoft likes to price its operating systems per CPU. Windows Home Edition (1 CPU license) costs less than Windows Professional (2 CPU license), which costs less than Windows Server (4 CPU license IIRC), which costs less than Windows Advanced Server, etc. Thus, the price of Windows is one factor in the drive to put as much processing power in one core as possible.

    --
    Will I retire or break 10K?
    1. Re:Microsoft prices its operating systems per CPU by Short+Circuit · · Score: 1

      Re: Photoshop on a cluster

      You could probably pull it off if you ran openMOSIX on the cluster, and the new multiprocessor VMWare under openMOSIX. (Which is just a set of patches to Linux to make a cluster look to applications as a single machine.)

      Re: More power to one core

      Now bring business and marketing tactics into play. Having a CPU that can handle multiple bundles is, performance-wise, much like having a CPU with HyperThreading or multiple cores. Microsoft sees a Hyperthreading CPU as two CPUs. Why would they feel inclined to price an OS that supports multibundle IA-64 CPUs the same as an OS that supports a single IA-32 CPU?

    2. Re:Microsoft prices its operating systems per CPU by yerricde · · Score: 1

      You could probably pull it off if you ran openMOSIX on the cluster, and the new multiprocessor VMWare under openMOSIX.

      VMWare is proprietary and very expensive per seat. Windows Server is proprietary and very expensive per seat. The price of licensing such software would probably be more expensive than just upgrading to the next faster single core. Besides, the proprietary filters in Photoshop were written with a low-latency UMA multiprocessor in mind, not a comparatively high-latency NUMA cluster.

      Why would they feel inclined to price an OS that supports multibundle IA-64 CPUs the same as an OS that supports a single IA-32 CPU?

      For the same reason the Windows OS was priced the same for 486 (one execute unit), Pentium (one pipe and one half-pipe), Pentium II/III (one pipe and two half-pipes), Athlon, and Pentium 4.

      --
      Will I retire or break 10K?
    3. Re:Microsoft prices its operating systems per CPU by Short+Circuit · · Score: 1

      My point is that multibundle CPUs, multilogical CPUs, and multiprocessor systems lend themselves to server tasks.

      Windows is priced on the theory that, as far as a customer is concerned, a parallel-processing system is going to be worth paying extra for the OS.

      With that in mind, I don't think Microsoft will want to soften its pricing system for a new CPU architecture. Assuming there's a way to detect how many simultaneous bundles an IA-64 CPU can handle, I see Microsoft preferring to charge different amounts for an OS that can support a different level processor.

    4. Re:Microsoft prices its operating systems per CPU by yerricde · · Score: 0, Flamebait

      Assuming there's a way to detect how many simultaneous bundles an IA-64 CPU can handle, I see Microsoft preferring to charge different amounts for an OS that can support a different level processor.

      And watch people stick a new processor in the motherboard and find that Windows now refuses to boot unless the user enters a credit card number.

      Once multithreading trickles down to even the entry-level processors, how will PC vendors be able to afford the Windows licenses for PCs sold to home users?

      --
      Will I retire or break 10K?
    5. Re:Microsoft prices its operating systems per CPU by Short+Circuit · · Score: 1

      That's a good question. And we're seeing some of the results.

      Best Buy and friends are selling machines with XP Home installed. These don't take advantage of HyperThreading on the latest Pentium 4s. People who are aware of the fact go out and buy XP Pro, but the rest don't know.

      PC Vendors can probably continue to get away with selling "crippled" PCs.

      An interesting technical question lays in whether the OS can control applications' access to multibundle functionality in the processor? I can only see that as possible if Microsoft comes out with another executable format, where bundle execution is scheduled by the OS.

      Alternatively, they could require that everything be run under the .NET interpereter, and control system usage from there.