> Once the genie is out of the bottle, backward compatibility means imitating the old instruction set.
Since the instructions are completely unofficial and only available through what I assume is a dynamically linked system framework, there is 0 chance Apple will care.
For prior art, when Apple silently decided to change the ABI of the syscall underlying gettimeofday(2) in Sierra, projects who made raw syscalls despite that never being officially supported (cough cough golang) had to fix their stuff.
That's fair. But i could see these instructions being useful for photoshop, lightroom, image magick, rendering software, video encoders, games physics etc. way beyond what their library offers. And if wager that Apple will be using those instructions under the hood of their own products.
> But i could see these instructions being useful for photoshop, lightroom, image magick, rendering software, video encoders, games physics etc. way beyond what their library offers.
So?
> And if wager that Apple will be using those instructions under the hood of their own products.
Which they can, whether through the public library they offer or through one of their private frameworks.
Since the instructions are completely unofficial and only available through what I assume is a dynamically linked system framework, there is 0 chance Apple will care.
For prior art, when Apple silently decided to change the ABI of the syscall underlying gettimeofday(2) in Sierra, projects who made raw syscalls despite that never being officially supported (cough cough golang) had to fix their stuff.