Slashdot Mirror
Linus on Intel's 64 bit Extensions
ceswiedler writes "KernelTrap is running a thread on the Linux-Kernel mailing list about Intel's new IA-32e 64-bit chip. Linus complains 'what I found so irritating is that _hours_ after the Intel announcement,
people were _still_ confused about whether the new intel chip was actually compatible with AMD's chips.' It is, of course, but you have to do a thorough comparison of Intel's reference manuals to discover that-- they don't mention the fact that their new chip is instruction-set compatible with AMD's x86-64 chip." See the previous story for background. So it looks like the reason Intel was vague about their announcement is that they didn't want the WORLD TO KNOW THAT THEY WERE COPYING AND FOLLOWING AMD rather than developing some new thing on their own. Slashdot is proud to help Intel in this quest; wouldn't want the public to know that INTEL WAS SIMPLY FOLLOWING IN AMD'S FOOTSTEPS. Hope this helps.
THIS ARTICLE SUMMARY NEEDS MORE UPPERCASE.
Lameness filter encountered. Post aborted!
Reason: Don't use so many caps. It's like MICHAEL SIMS BLOWING A GASKET.
for clarification :)
Now slashdot will clarify things that businesses cannot ;)
I could change the world, but GOD won't give me the source code
Whoa easy on the caps there cowboy :)
Nobody smart reads Slashdot, otherwise the goose is loose.
If there was any doubt that Slashdot is a valid news source, those fears can now be LAYED TO REST.
Everything seemed to be going so nice
'till the end of all beings punched right through the ice
All your instructions are belong to us.
500GB of disk, 5TB of transfer, $5.95/mo
I'd rather have AMD be the leader than Intel. I've always been happy with AMD, seeing as how they don't bloat the appearance of speed on their cards to the average dolt at the expense of clear technical data.
http://mediagoblin.org/
Up until recently, AMD has had to follow in Intel's footsteps. They have been forced to use Intel's extensions for years- until this (VERY) bold move by them. Now, the tables are turned, and Intel are backed into the corner instead of AMD. I love it.
Listen to my experimental-industrial-techno!
Since when has reading articles been a requirement of posting in any given Slashdot article?
All your customer are belong to us ;)
"Hey! Unless this is a nude love-in, get the hell off my property!!"
Even back in the Apple ][ days when you had no choice in the matter?
I didn't see it as: unimportant/important.
...which makes it even funnier...
I saw it as: quiet/LOUD!
(Stolen sig) Remember: it's a "Microsoft virus", not an "email virus", a "Microsoft worm", not a "computer worm
but does anyone else find IA-32e to be a STUPID name for a 64-bit processor?
Even in those days, not everyone did things half-ASCII.
One line blog. I hear that they're called Twitters now.
I'd like to see an AMD commercial (with the Blue Man Group) that hypes up Intel Inside, only at the end to show an Intel CPU with a little AMD Inside sticker on it.
First HP makes PA-RISC. This turns out to be a kick-ass architecture with a lot of room to grow. Years go by and Intel enters into a partnership with HP to develop PA-RISC into Merced... nee Itanium. This is good. Intel of course bojos everything up and many millions of dollars later, we have really kick-ass PA-RISC chips and Itanium 1 which nobody gives a rats ass about. Some improvement later and we still have some even more kick-ass HPPA chips and Itanium 2 and its ilk.
Then $SUIT_IN_THE_EXTREME Carly decides after buying CornPACK and Tandem to say F*** all common sense... we have this next-gen PA-RISC design called MAKO and our current Superdomes that outperform Itanium 2 (but shhh don't publish those results)... lets throw it all out... HPPA, MIPS (Himalaya), Alpha, yes all the good processor technology we own... to be dependent on Intel who has no prior experience with 64 bits other than our partnership that makes crappy chips and bet the farm on Intel as being the bomb diggity of 64-bitness.
Now Intel realizes... WE GOOFED big time. WE HUFFED the SCO crack-pipe... lets make x86-64 (one big head smack for the obvious not occurring to them earlier, and another one for extending the life of x86 even farther). WHERE does this leave both Intel (with IBM and POWER4/5/6+ spanking their asses back to the stone age) and poor (NOT) HP who bet the farm on Itanic 2... ?
Oh this is too good.
I hope they both sink in the same boat.
and for AMD's sake I hope they add a fs*ckin thermistor to their procs so if the heat sink is loose they don't smoke themselves... (fsckin unacceptable).