I wonder how comparable Geekbench actually is across different CPU architectures and operating systems though?
Linus Torvalds is quoted here: https://www.realworldtech.com/forum/?threadid=185109&curpost... as saying that Geekbench 4.0 shouldn't be treated as a valid comparison between desktops/laptops and phones. (However this review used Geekbench 5.0 - not sure what differences there are).
Floating point tends to matter for classic 'number crunching' workloads- crypto, media encoding, anything to do with modeling the physical world, image processing, AI.
Phones tend towards 'control flow', e.g. display an interface, accept a user input, communicate with a server, display information... and media decoding & gps both have dedicated hardware.
FP workloads can be incredibly power hungry, so it's fortunate mobile devices mostly manage to avoid them. But any chip with an FP unit is going to shut it off when running integer code.
Crypto stuff never uses floating point. It might have built-in instructions like AES-NI, though. In the test geekbench consider that - integers ones[0] and definitely not floating point. Media encoding tend not to use floating point, either. (decoders tend to be built-in in the GPUs with designated hardware, so testing on CPU is quite pointless)
SSE/AVX has its own set of registers. It can do floating point and integer operations. It would not be correct to refer to it as a floating point unit.
GPUs are good at mining because they can do so many calculations in parallel. They're just as capable of integer operations as the SIMD units on a CPU.
Yeah, "statically linked" is a bizarre thing to say about iOS. I believe the only statically linked code on iOS is dyld itself. It's not possible to make a statically linked app on iOS, and certainly all the number crunching routines (and compression etc.) are dynamically linked. Maybe geekbench doesn't link them and does it in-process? But you would see the same effect on PCs then.
Linus Torvalds is quoted here: https://www.realworldtech.com/forum/?threadid=185109&curpost... as saying that Geekbench 4.0 shouldn't be treated as a valid comparison between desktops/laptops and phones. (However this review used Geekbench 5.0 - not sure what differences there are).