4 ms·
But if it is undocumented Apple has no obligation to support these instructions in user code. In fact you will most likely get a fail trying to submit this to t
by socialdemocrat 6y ago
But if it is undocumented Apple has no obligation to support these instructions in user code. In fact you will most likely get a fail trying to submit this to the app store.
Apple has always been merciless on this. If you use stuff they don't support and your software later breaks, that is your problem.
This is different from say Microsoft which has added support for quirks and bugs in software in their OS updates to keep old software running.
Apple doesn't do that, and I think it is the right decision. It makes developers used to following standards. But it is a tough call as it really pisses off people when their software breaks due to OS updates.
- mkr-hn 6y agoI wonder if Apple would be as concerned with backward compatibility if they had Microsoft's reach in governments and enterprise. Enormous organizations are probably not receptive to "it's your own fault for using undocumented behavior" when negotiating contracts.
- temac 6y agoYou don't negitiate contracts about OS promising backward compat. Not even MS, which has a quite good backward compat story for windows, does that. Plus pro apps are often specified and tested to run on a specific OS version.
- h0l0cube 6y ago> Apple doesn't do that, and I think it is the right decision. It makes developers used to following standards. But it is a tough call as it really pisses off people when their software breaks due to OS updates. But why not support it at the bitcode level? Matrix operations have broad applicability, so they are just slowing down the software for customers using third party products that could use those instructions beyond what the library offers.