Re:ARM MacBook vs. Intel MacBook: A SIMD Benchmark
by onedognight on Sunday December 13, 2020 @02:31PM
(#25409361)
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.
Re:ARM MacBook vs. Intel MacBook: A SIMD Benchmark
by dirtypersian on Sunday December 13, 2020 @03:12PM
(#25409765)
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?
Re:ARM MacBook vs. Intel MacBook: A SIMD Benchmark
by bwasti on Sunday December 13, 2020 @04:02PM
(#25410243)
You can just try the instructions with an off-the-shelf assembler. They're not supported.
Re:ARM MacBook vs. Intel MacBook: A SIMD Benchmark
by saagarjha on Sunday December 13, 2020 @06:47PM
(#25411693)
Unless you have to toggle an MSR, of course…
Re:ARM MacBook vs. Intel MacBook: A SIMD Benchmark
by andy_ppp on Sunday December 13, 2020 @04:22PM
(#25410414)
I’m kind of interested about what happens if you throw random opcodes at processors now!
Re:ARM MacBook vs. Intel MacBook: A SIMD Benchmark
by aw1621107 on Sunday December 13, 2020 @04:54PM
(#25410722)
You might be interested in sandsifter [0], which does precisely that!
Re:ARM MacBook vs. Intel MacBook: A SIMD Benchmark
by dirtypersian on Sunday December 13, 2020 @04:45PM
(#25410628)
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.
[1] https://community.arm.com/developer/tools-software/hpc/b/hpc... [2] https://community.arm.com/developer/ip-products/processors/b...