4 ms·

I assume SVE [1]/ SVE2 [2] will be implemented in future Apple Silicon processors. Possibly along with ARMv9. [1] https://community.arm.com/developer/tools-sof

I assume SVE [1]/ SVE2 [2] will be implemented in future Apple Silicon processors. Possibly along with ARMv9. [1] https://community.arm.com/developer/tools-software/hpc/b/hpc-blog/posts/technology-update-the-scalable-vector-extension-sve-for-the-armv8-a-architecture https://community.arm.com/developer/tools-software/hpc/b/hpc... [2] https://community.arm.com/developer/ip-products/processors/b/processors-ip-blog/posts/new-technologies-for-the-arm-a-profile-architecture https://community.arm.com/developer/ip-products/processors/b...

onedognight 6y ago
SVE is interesting because it gives you forward binary compatibility. i.e. your binary, written for a 128bit wide vector unit, will benefit directly from a newer 256bit wide unit without recompilation.
dirtypersian 6y ago
Who says they don't already support SVE; is it publicly known they support it or not? Especially if the binary doesn't have to be recompiled you'd never know whether they implemented it or not right?
- bwasti 6y ago
  You can just try the instructions with an off-the-shelf assembler. They're not supported.
  - andy_ppp 6y ago
    I’m kind of interested about what happens if you throw random opcodes at processors now!
    - dirtypersian 6y ago
      I would guess the processor would just cause an exception/interrupt and it would just call an OS level exception/interrupt handler which would probably tell the user what the exception/interrupt was that occured; in this case an unsupported instruction.
    - nicoburns 6y ago
      I believe most processors have undocumented opcodes. Often used for internal debugging or similar.
    - aw1621107 6y ago
      You might be interested in sandsifter [0], which does precisely that! [0]: https://github.com/xoreaxeaxeax/sandsifter https://github.com/xoreaxeaxeax/sandsifter
    - grishka 6y ago
      Your program will crash with SIGILL.
  - saagarjha 6y ago
    Unless you have to toggle an MSR, of course…

onedognight 6y ago

SVE is interesting because it gives you forward binary compatibility. i.e. your binary, written for a 128bit wide vector unit, will benefit directly from a newer 256bit wide unit without recompilation.

dirtypersian 6y ago

Who says they don't already support SVE; is it publicly known they support it or not? Especially if the binary doesn't have to be recompiled you'd never know whether they implemented it or not right?

bwasti 6y ago
You can just try the instructions with an off-the-shelf assembler. They're not supported.
- andy_ppp 6y ago
  I’m kind of interested about what happens if you throw random opcodes at processors now!
  - dirtypersian 6y ago
    I would guess the processor would just cause an exception/interrupt and it would just call an OS level exception/interrupt handler which would probably tell the user what the exception/interrupt was that occured; in this case an unsupported instruction.
  - nicoburns 6y ago
    I believe most processors have undocumented opcodes. Often used for internal debugging or similar.
  - aw1621107 6y ago
    You might be interested in sandsifter [0], which does precisely that! [0]: https://github.com/xoreaxeaxeax/sandsifter https://github.com/xoreaxeaxeax/sandsifter
  - grishka 6y ago
    Your program will crash with SIGILL.
- saagarjha 6y ago
  Unless you have to toggle an MSR, of course…