Download the Tom's Hardware App from the App Store
The reference for current tech news
Yes No
Ads

AMD Drops 3DNow! Support From Future CPUs

by - source: Tom's Hardware US

3DNow! has become 3DNo More!

It really doesn't feel like it was that long ago when AMD introduced its own SIMD extensions called 3DNow!, but it's been long enough now that the chip company is sending the technology out to pasture.

AMD announced last week that 3DNow! is deprecated and will not be supported in certain upcoming AMD processors and will not have that feature flag bit set.

What does this mean for those who make software using these AMD instructions?

If your software used 3DNow! instructions at any point in time you should confirm that you only take that code path after checking to see if the feature is supported during runtime, using CPUID.

Most likely, your code already has another code path to take, such as an SSE path, if 3DNow! instructions are not supported.  To reiterate, make sure that the code uses feature bits to determine when the code should take this path.  If the code uses the vendorID string rather than a feature bit to make the path determination, AMD processors that support SSE may end up taking a slower path as a result.

Read the full post from the AMD developer blog.

Share:
38
Comments
Read more
X
Submit

Comments
Add your comment
decode 08/24/2010 2:19 PM
Hide
-15+

Barely even knew about this feature, except that I had it, Lol!

pogsnet 08/24/2010 2:33 PM
Hide
-14+

This feature started before SSE comes out in Pentium III era

jj463rd 08/24/2010 2:34 PM
Hide
-20+

Oh yeah I remember the 3DNow extensions on my old K6-2 CPU from 1998.

San Pedro 08/24/2010 2:39 PM
Hide
-16+

Those of you playing still playing Quake 2 (wouldn't blame you) are out of luck.

Mottamort 08/24/2010 2:44 PM
Show
Baracubra 08/24/2010 2:57 PM
Show
ajcroteau 08/24/2010 3:07 PM
Hide
-9+

3DNow was huge back in the day... I had a couple of K6-2 cpu's and both ran fairly well... but it looks like it's gone the way of the dinosaurs...

mavroxur 08/24/2010 3:08 PM
Hide
-20+

3DNow! has been surpassed by....how many code extensions? And if your software supported 3DNow!, the software will still run, just without the extensions now. Which might be a performance issue....if your software wasn't 15 years old and designed to run on K6-2 CPU's anyways. So the 10% performance hit you take from no 3DNow! will be canceled by the 1000000% performance gain from a modern CPU :-)

Xatos 08/24/2010 3:21 PM
Hide
-16+

^ Exactly.

COLGeek 08/24/2010 3:45 PM
Hide
-2+

Things change. 3DNow! served its purpose and that is now behind us. In the day, 3DNow! was cool, but not often used so its passing at a time when CPUs are so much more advanced could have passed without an AMD announcement (except in the old dude SW dev world). BTW, I am one of those old dudes.

Shin-san 08/24/2010 3:50 PM
Hide
-7+

This makes sense. There have been so many CPU extensions like SSE that have replaced 3DNow! It's actually a requirement that SSE2 is standard in x64 CPUs

chick0n 08/24/2010 3:54 PM
Hide
-9+

Losing 3Dnow! is not really a big deal. We have all these fast CPU and now even GPU will be able to help crunching numbers really really fast.

but my question is, does it take that much of a resource to "keep" 3Dnow! extension in the CPU logic? or is it causing some of the problems ?

only AMD knows.

rocky1234 08/24/2010 4:03 PM
Hide
-3+

Well even though it served it's purpose back in the day I do not think many or if any modern programs use it any longer. So if this makes more die space so AMD can ad other features into their CPU's I am all for it.

I'm sure Quake 2 will run fine still without it..lol :)

Sorax 08/24/2010 4:17 PM
Hide
-4+

I played the original Half-Life on a K6-2 in 1998. And continued to use it for years with TF and CS. So thanks for the wonderful memories 3DNow!

COLGeek 08/24/2010 4:36 PM
Hide
-1+

I actually still have a K6-2+ based Sony Vaio at home with a whopping 256MB of RAM running Puppy Linux. When we bought it for my wife, it was state of the art and came pre-loaded with Windows ME (that was removed within minutes of opening the box and replaced with Win2K).

Even so, if I had to guess, the 3DNow! extensions were likely never used on this machine as it was never used for games.

Regardless, it is cool to discuss these changes in the tech landscape.

harth13 08/24/2010 4:41 PM
Hide
-2+

wikipedia says "The 3DNow! instruction set was created during the late 1990s when 3D graphics were exploding in popularity because of 3D gaming, and 3D games heavily use floating-point arithmetic."

and i say old

Anonymous 08/24/2010 5:16 PM
Hide
--2+

AMD could have easily updated the 3D Now instruction set but for one reason, fusion, any amount of SSE will never come near to the power of a real gfx processor

now i have to wonder if GPGPU does take off, will it make SSE new and old obsolete

iggybeans 08/24/2010 5:30 PM
Show
orionantares 08/24/2010 5:38 PM
Hide
-1+

No surprise. AMD simpl wasn't extending 3DNow instead they were working wth Intel's SSE and helped extend that once or twice, especially in the AMD64 architecture.

2real 08/24/2010 5:56 PM
Hide
-8+

iggybeans :
As this decision affects backward compatibility, I personally view it as a negative.


are you thick? you can still play the games you'll just get 500 fps instead of 550

Anonymous 08/24/2010 5:57 PM
Show
steelbox 08/24/2010 6:15 PM
Hide
-1+

Oh, Brings me back.

nforce4max 08/24/2010 6:16 PM
Hide
-1+

The reason behind 3DNow and SSE was to improve performance. On the Intel side performance increased by 60% just by adding the instruction sets even on a clock by clock bases with the same core. You all can look up old articles about this or do lot of benchmarking on vintage systems to see it's impact. Modern cpu get most of their performance from SSE while AMD's 3DNow if optimized can see big gains but that is a waste knowing market share. Basically what these instruction sets do is allow the FPU to cheat in certain calculations and reduce the time needed to complete them. Some can be scripted for encryption or multimedia decoding ect. However there are limits and to how much scripting can be done as well the limits of the architecture of the cpu core/s. This is why emulation of different platforms such as Power PC, Amiga, and many game consoles are so difficult.

The First cpu to include such scripting for the improvement of performance was the Zilog Z80.

rhino13 08/24/2010 7:23 PM
Hide
-0+

Sad really, I mean has Intel dropped MMX?

jimmysmitty 08/24/2010 7:53 PM
Hide
-2+

jj463rd :
Oh yeah I remember the 3DNow extensions on my old K6-2 CPU from 1998.



Yep. It was sor of AMDs version of MMX. Then when SSE came out, AMD has a tech trade agreement with Intel so they both have SSE.

TOo bad. Was a good feature set. But its seen its time much like other technology.

Honis 08/24/2010 7:58 PM
Hide
-2+

chick0n :
Losing 3Dnow! is not really a big deal. We have all these fast CPU and now even GPU will be able to help crunching numbers really really fast.but my question is, does it take that much of a resource to "keep" 3Dnow! extension in the CPU logic? or is it causing some of the problems ? only AMD knows.


It takes up some (unknown to us) amount of space in the processor. I doubt its anything that we looking at specs will be able to say "Ah hah! They were able to add another 256 KB of L1 cache!"

Considering it's an AMD only extension set I'm not surprised. The performance hit will be minimal considering a modern CPUs raw speed.

Assmar 08/24/2010 8:40 PM
Hide
-3+

ajcroteau :
3DNow was huge back in the day... I had a couple of K6-2 cpu's and both ran fairly well... but it looks like it's gone the way of the dinosaurs...


3DNow evolved into the birds we know and love today!? Fascinating.

rooket 08/24/2010 9:02 PM
Hide
-0+

San Pedro :
Those of you playing still playing Quake 2 (wouldn't blame you) are out of luck.



I was playing this game on N64 a couple days ago :D

Anonymous 08/24/2010 9:45 PM
Hide
-1+

Ahhhhh 3DNow, I'll miss you! Still remember the first time I patched Quake2 with 3dnow update and got like an extra 20fps. Holy crap that was impressive. Bumped my FPH (frags per hour, common measurement back in the day) from like 80-130.

ta152h 08/24/2010 10:48 PM
Hide
-1+

I think people miss the point on this. There's no penalty for losing 3D Now!, because nothing used it. Maybe 12 year old software did, but, I'm pretty sure you're not going to have a big problem running it on x87, on a modern processor.

By the way, x87 and MMX are dead as well. They are not part of x86-64, so can only be used in 32-bit mode. As time goes on, 64-bit will become dominant (just as we see very few Real Mode, or 286 Protected Apps today), so that pretty much all the old instructions will be at least deprecated.

However, the big difference is, x87, 286 Protected (mainly for extended memory support) and Real Mode were extensively used at one point, whereas 3D Now! never received much support, and was quickly supplanted by SSE when it came out, which was superior (mainly because AMD couldn't make the drastic changes Intel could and get industry support), and was backed by a much larger market share.

AMD saved money, and electricity by removing this worthless logic. It's a very good move. I hope they make their x87 unit smaller as well, since SSE2 and later should always be used now, instead of it.

iam2thecrowe 08/25/2010 12:41 PM
Hide
-3+

San Pedro :
Those of you playing still playing Quake 2 (wouldn't blame you) are out of luck.


there was a 3d now patch for this. Worked great for my old K6-2, which I think I still have lying around somewhere.


Ads

Best offers

Newsletters


OK
Ads