3 ms·
I don't think many people have a problem with special case, highly-complex instructions when they make a lot of sense. Reading into FJCVTZS leads me to believe
by bob1029 6y ago
I don't think many people have a problem with special case, highly-complex instructions when they make a lot of sense. Reading into FJCVTZS leads me to believe that this is a fairly common use case for a type of code execution that could hypothetically occur with any arbitrary website on any ARM device (aka smartphones). I also assume this instruction does not restrict the clock speed of the CPU based on its behavior or otherwise impact the general case adversely. The availability of this instruction likely only improves the experience of the user when utilized.
I personally have a problem when compromises are made for the general case to satisfy a special case, especially when the special case motivations appear to be bound mostly in marketing reasons. Even more so if the special case is well-known to adversely impact performance in the general case.
Before I saw this post, I didn't even know ARM had some complex javascript instruction. Contrast that with - You can't watch or read a review for any current gen Intel server product without being presented with at least one AVX benchmark. Is this marketing or is it practical engineering? For how many applications is AVX availability actually a hard constraint?