• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Question Zen 6 Speculation Thread

Page 402 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
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.
that discussion was for client. I said AVX-512 has many benefits in HPC. In client not so much, unless you emulate PS3 games. Most people don’t do that so what do you mean by average applications?

Most average applications don’t even touch AVX2
 
In client not so much, unless you emulate PS3 games.
While we were looking for a way to create soft and realistic shadows on tanks, our long-standing partner, Intel, offered to share their expertise and to assist us. Intel Advanced Rendering engineers helped with high-performance kernels and optimizations. Thanks to concurrent rendering support and the ability to parallelize the rendering we implemented in Update 1.4, the Intel Embree technology was perfect for our game.

It's been said before on the forum, Intel mistakenly used AVX as yet another product segmentation tool. They should have made it ubiquitous across their ecosystem, it would have paid a lot more in the long run.
 
It's been said before on the forum, Intel mistakenly used AVX as yet another product segmentation tool. They should have made it ubiquitous across their ecosystem, it would have paid a lot more in the long run.

Celeron and Pentium (and the Atoms) not having AVX should not have prevented AVX adoption.
 
Celeron and Pentium (and the Atoms) not having AVX should not have prevented AVX adoption.
It's not just Celerons and Pentiums. It all started with Skylake-X when intel added AVX-512 support in server and HEDT, but not client. In the 9 years since then AVX-512 support has been spotty. They had a few years of AVX-512 support for some of their mobile line-up, (Ice Lake and Tiger Lake iirc), but not desktop. And then they moved to heterogeneous cores in 2021 and won't support it again in client until 2027.
 
So how do you think, will Zen 6 be a match for CCC? https://chipsandcheese.com/p/embracing-ai-with-claudes-c-compiler 😉
Drew Confuse Face What Meme GIF
 
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.

The issue with AVX-512 is adoption if there is no HW what's the point of writing software for it in client.

The reason why I brought up AVX10 specifically is that you should be able to support 128b, 256b, and 512b instruction/data paths with one codebase. You really had to go out of your way to support AVX-512 which is something most developers were not prepared to do, especially when it was largely absent from client CPUs for a long time.
 
  • Like
Reactions: 511
The reason why I brought up AVX10 specifically is that you should be able to support 128b, 256b, and 512b instruction/data paths with one codebase.
From practical point of view you can do that with AVX512, as only Xeon Phi does not support 128b/256b AVX512 extension afaik. Yes you need to check one more flag for dynamic dispatch compared to AVX10 but I would say that's hardly a problem.

You anyway need to have explicit kernels for 128b/256b/512b instruction usage if for one reason or another use of masking would not be appropriate regardless if it is AVX512+extensions or AVX10.
 
The reason why I brought up AVX10 specifically is that you should be able to support 128b, 256b, and 512b instruction/data paths with one codebase. You really had to go out of your way to support AVX-512 which is something most developers were not prepared to do, especially when it was largely absent from client CPUs for a long time.
I think that Intel is using AVX10 as a way of mitigating their huge losses against AMD where AVX512 is being utilized. I suspect they had to think long and hard about how to make an instruction set that allowed MUCH smaller transistor budgets to exist in their little cores, but still perform the same code operations .... just much slower.

Correct me if I am incorrect, but all you have to do to get AVX-512 support is use a compiler that supports it. Then it gets used if the hardware exists to use it. I suspect it is pretty uniform by now.
No, that is desd.
AVX10 is 512b only.
Since I know that adroc will never actually support his own assertions, could someone else please explain to me with links if this is or is not true? Last time I dove in, this was blatantly NOT true.
 
Since I know that adroc will never actually support his own assertions, could someone else please explain to me with links if this is or is not true? Last time I dove in, this was blatantly NOT true.
here is the latest AVX 10 spec
also this
 
Back
Top