Well it's kind of needed cause there are absolutely some stuff that can make use of extra GPR and the new instructionsThey did!
But a lot of times, you gotta compromise.
Well it's kind of needed cause there are absolutely some stuff that can make use of extra GPR and the new instructionsThey did!
But a lot of times, you gotta compromise.
Not the problem.Well it's kind of needed cause there are absolutely some stuff that can make use of extra GPR and the new instructions
Than what's the problem ?Not the problem.
It's not a clean ISA break like aa64 was.Than what's the problem ?
X86_64 sells in the name of compatibility and they probably decided Compatibility is more important for them.It's not a clean ISA break like aa64 was.
A stupid half-measure no one really asked for.
You're not forced to remove amd64! APX is already incompatible anyway from compiler POV.X86_64 sells in the name of compatibility and they probably decided Compatibility is more important for them.
IIRC during that period Intel castrated some Core CPU with AVX2 removed.Well this is primarily down to Atom guys being really really annoying about it.
APX is a ABI Extension not a clean break like AA64 was over AA32You're not forced to remove amd64! APX is already incompatible anyway from compiler POV.
ffs stop with this stupid garbage. aa32 did not die to aa64.
AVX512 but yes.IIRC during that period Intel castrated some Core CPU with AVX2 removed.
THAT.APX is a ABI Extension not a clean break like AA64 was over AA32
AMD did the same thing with AMD64 16 GPRTHAT.
IS. THE.
P R O B L E M.
32 arch GPRs and a new prefix already smash compiler assumptions so there was no reason to not do a clean ISA break with a separate exec mode. Alas, Intel is a thing.
Yes and brought a bunch of issues down the line.AMD did the same thing with AMD64 16 GPR
Haswell/Skylake Pentiums lacked AVX2 though.AVX512 but yes.
Skylake is almost 11 years old, though.Haswell/Skylake Pentiums lacked AVX2 though.
Cough cough Rocket lake cough coughAVX-512 was supposed to be mainstreamed but ala 10nm happened.
Yeah, wasn't until Tiger Lake on notebooks and Alder Lake on desktop that 'Pentium' and 'Celeron' branded big "Core" SKUs got up to AVX2.Haswell/Skylake Pentiums lacked AVX2 though.
DRAM prices are 50% up next Q.Now that news broke that Sam Altman may have manipulating the DRAM market broke, how might this impact predictions?
Is there any talk of any action around what he did?Now that news broke that Sam Altman may have manipulating the DRAM market broke, how might this impact predictions?
I was more concerned about its impact to Zen 6 speculation. People were accepting low RAM sizes for the average purchase. OpenAI is a dead man walking after the future SaaS news a little while back. One AI is about to win a huge chunk of the market and it is not his.Is there any talk of any action around what he did?
This Coffee Lake CPU from 2020 doesn't have AVX2:AVX512 but yes.
isn't this atom?This Coffee Lake CPU from 2020 doesn't have AVX2:
Intel® Celeron® Processor G4950 (2M Cache, 3.30 GHz) - Product Specifications | Intel
Intel® Celeron® Processor G4950 (2M Cache, 3.30 GHz) quick reference with specifications, features, and technologies.www.intel.com
It clearly states:isn't this atom?
Arrow Lake U exists so i can't take this seriously but based on stepping looks like it's a stepping without AVX2 at allIt clearly states:
Arguing that people don't need faster and more efficient computing is kinda silly don't you think? This isn't like the more cores argument since many high performance required applications and average applications use AVX 512. The disadvantage is only in transistor count in the cpu cores.Do you need AVX-512 for that?
Edit: let me rephrase, do people who buy client CPUs ever need the performance that AVX-512 provides for JSON parsing e.g simdjson?
I don't think applications are going to STOP using it. If anything, it will work with AVX 10. Intel started the AVX512 instruction set direction, lots of applications have adopted it.Why would anyone bother using AVX-512 when many CPUs don’t support it at all?
This, alongside Intel’s initial suboptimal implementations, is the reason why AVX-512 has been so slow to catch on.
Yes, but it is compatible with AVX512. It simply expanded the instructions to be many different bits wide so that the Intel little cores can still execute the instructions without the larger transistor budget. Still, the BEST way to execute AVX 10 is by supporting a 512bit wide AVX instruction and data path.Pardon my ignorance but in the future, won't software developers be targeting something like AVX10 or whatever anyway?
LOL. It came up in my news feed today as well. Had me for a moment, then reality took over 🙂