Re:Intel's make-or-break 18A process node debuts for data ce...
by georgeburdell on Tuesday March 03, 2026 @02:29PM
(#47237583)
E core vs P core is an internal power struggle between two design teams that looks on the surface like ARM’s big.LITTLE approach
[ Parent
| on HN ]
Re:Intel's make-or-break 18A process node debuts for data ce...
by Aardwolf on Tuesday March 03, 2026 @02:35PM
(#47237711)
E cores ruined P cores by forcing the removal of AVX-512 from consumer P cores
Which is why I used AMD in my last desktop computer build
Re:Intel's make-or-break 18A process node debuts for data ce...
by mort96 on Tuesday March 03, 2026 @03:41PM
(#47238655)
E cores didn't just ruin P cores, it ruined AVX-512 altogether. We were getting so close to near-universal AVX-512 support; enough to bother actually writing AVX-512 versions of things. Then, Intel killed it.
Re:Intel's make-or-break 18A process node debuts for data ce...
by jsheard on Tuesday March 03, 2026 @03:29PM
(#47238500)
That's finally set to be resolved with Nova Lake later this year, which will support AVX10 (the new iteration of AVX512) across both core types. Better very late than never.
Re:Intel's make-or-break 18A process node debuts for data ce...
by bmenrigh on Tuesday March 03, 2026 @03:05PM
(#47238156)
I love the AVX512 support in Zen 5 but the lack of Valgrind support for many of the AVX512 instructions frustrates me almost daily. I have to maintain a separate environment for compiling and testing because of it.
Re:Intel's make-or-break 18A process node debuts for data ce...
by paulf38 on Wednesday March 04, 2026 @01:20AM
(#47243828)
There was someone at Intel working on AVX512 support in Valgrind. She is/was based in St Petersburg. Intel shuttered their Russian operations when Putin invaded Ukraine and that project stalled.
If anyone has the time and knowledge to help with AVX512 support then it would be most welcome. Fair warning, even with the initial work already done this is still a huge project.