Intel completely disables AVX-512 on Alder Lake after all
1–10 of 317 posts
Re: Intel completely disables AVX-512 on Alder Lake after all
#2Is this not the definition of bait and switch? How can this not end up in a lawsuit and investigation from regulatory bodies ?
Re: Intel completely disables AVX-512 on Alder Lake after all
#3Is this not the definition of bait and switch? How can this not end up in a lawsuit and investigation from regulatory bodies ?
This is an undocumented feature, from what I gather. So it's missing the "bait" part of "bait and switch".
Re: Intel completely disables AVX-512 on Alder Lake after all
#4Is this not the definition of bait and switch? How can this not end up in a lawsuit and investigation from regulatory bodies ?
This is an undocumented feature, from what I gather. So it's missing the "bait" part of "bait and switch".
It's not even undocumented, but explicitly a documented as a feature those CPUs don't have. Originally it was supposed to be fused off physically, I wonder why it wasn't.
Re: Intel completely disables AVX-512 on Alder Lake after all
#5Is this not the definition of bait and switch? How can this not end up in a lawsuit and investigation from regulatory bodies ?
This is an undocumented feature, from what I gather. So it's missing the "bait" part of "bait and switch".
The performance benchmarks of the Alder Lake is far from undocumented at this point.
Re: Intel completely disables AVX-512 on Alder Lake after all
#6Is this not the definition of bait and switch? How can this not end up in a lawsuit and investigation from regulatory bodies ?
This is an undocumented feature, from what I gather. So it's missing the "bait" part of "bait and switch".
I'm not sure if benchmarks that are out have the AVX-512 enabled or not.
If they do then this is indeed fraud.
They can always claim that those were engineering samples and not meant to be tested, but, I think they knew.
But: that's assuming a lot. It's possible that the ES chips sent to reviewers also had AVX-512 disabled, and that benchmarks did not make use of the instruction anyway.
Re: Intel completely disables AVX-512 on Alder Lake after all
#7Is this not the definition of bait and switch? How can this not end up in a lawsuit and investigation from regulatory bodies ?
It was never advertised, and Intel very specifically said AVX-512 instructions will not be available. Some motherboard manufacturers made them available anyway, now Intel is fixing that.
It's like buying a car with an advertised speed limiter of 155mph, then finding that actually it can go 170mph, and then the manufacturer fixes the speed limiter with a software update. Yes we know the car could go faster, but the speed limited version is the one that was actually advertised.
Re: Intel completely disables AVX-512 on Alder Lake after all
#8Unsurprising given their history regarding such moves.Kind of sad, some people in the linux community knew about the fact that alder lake is avx-512 capable.Also even if they did not advertise the product with this feature, can't they still be sued for worsening a product post-purchase?
Intel/AMD(though i can't remember AMD doing this in the last 5+ years) forcing motherboard vendors to effectively brick and disable features from consumers sounds like shouldn't be possible. You don't buy the CPU as a subscription to compute, you buy it as a product.
Re: Intel completely disables AVX-512 on Alder Lake after all
#9Earlier quoted context omitted.
This is an undocumented feature, from what I gather. So it's missing the "bait" part of "bait and switch".
The performance benchmarks of the Alder Lake is far from undocumented at this point.
You had to explicitly turn it on through hacks in the BIOS some motherboard makers added. If people enable a feature that's explicitly not supported on their benchmark rigs without disclosing it, that's not the vendors fault.
Re: Intel completely disables AVX-512 on Alder Lake after all
#10Stuff like this is why I plan to never buy Intel ever again. I always disliked Intel's strategy for market segmentation by disabling specific instructions, I much prefer AMD's strategy of segmenting just by speed and number of cores. It is really annoying that with Intel you can't run the same program on the server and on your desktop, it makes development and testing a huge pain.