News for hackers. Stuff that matters.
Re:A Big Week for RISC-V by colejohnson66 on Sunday February 13, 2022 @08:21AM (#30321585)
Forgive my ignorance if there’s an answer, but for x86, those extensions don’t overlap (mainly because Intel and AMD avoid stepping on each other). RISC-V doesn’t have a guarantee of non-overlapping vendor extensions, no?
Re:A Big Week for RISC-V by dzaima on Sunday February 13, 2022 @08:33AM (#30321651)
There's no way to prevent overlapping extensions. One could easily make an x86 extension that overlaps with some existing one. There's just as much an incentive to not do that for x86 as there is for RISC-V.

See AMD's SSE5 vs Intel's SSE4 conflict in x86 - both have instructions that the other doesn't have, and some that both have, and, from what I understand, even the instruction formats conflict.

Re:A Big Week for RISC-V by saagarjha on Sunday February 13, 2022 @08:45AM (#30321729)
> One could easily make an x86 extension

One cannot easily make an x86 extension because there are approximately ~3 entities on the planet allowed to make x86 extensions.

Re:A Big Week for RISC-V by sudosysgen on Sunday February 13, 2022 @11:26AM (#30322849)
Not really, China also added their own crypto extensions to x86 chips, though under AMD/VIA's license.

I wouldn't be surprised if Sony/Microsoft did too for their consoles.

It's doable if you have enough money to get AMD or VIA to make you a one-off.

Re:A Big Week for RISC-V by dzaima on Sunday February 13, 2022 @08:52AM (#30321759)
Here's my random x86 extension: the byte sequence 0xc5,0xfd,0xd4,0x00 sorts the 64-bit floats in ymm0. It conflicts with AVX2. :)
Re:A Big Week for RISC-V by saagarjha on Sunday February 13, 2022 @09:03AM (#30321815)
You’ll have trouble shipping that extension. Not because it conflicts with AVX2, but because Intel will sue you for your comparability with the rest of x86.