QEMU is always going to focus on emulation fidelity first and there are few shortcuts. With floating point the differences aren't generally in the numbers but in how the NaNs and other edge cases are handled. If you want to execute FP heavy code you should be cross compiling anyway.
QEMU absolutely will use hardware floating point where it can but only when it will give the correct results. FEX and Box64 are user mode emulators which achieve their speed by avoiding emulation where they can buy thunking at API boundaries.
They won't directly support it because in their view the Google Play process is a more secure way of verifying they supplied the binaries than is possible of f-droid. If reproducible builds were possible maybe there could be some mechanism to verify a given binary is built from a given commit of the source tree.
Pretty much. From v8.0 onwards all the extra features are indicated by id flags. Stuff that is relevant to kernel mode will generally be automatically handled by the kernel patching itself on booting up and in user space some libraries will select appropriately accelerated functions when the ISA extensions are probed. There are a bunch off advisory instructions encoded in the hint space that will be effectively NOPs on older hardware but will enhance execution if run on newer hardware.
If you want to play with newer instructions have a look at QEMUs "max" CPU.
Virt-manager isn't super scriptable but the underlying libvirt can be controlled by virsh which is a shell interface to libvirt. You can use both at the same time, e.g. start and stop via virsh and access to gui container via virt-manager/virt-viewer.
It does read like some long diatribe by someone who's salty about paying taxes. I guess they aren't worried about all the public services they pay for. I'm sure their monero will keep them warm into their dotage.
For that £9 I get 15Gb of data (including EU roaming). One of my kids gets their phone with unlimited calls/texts + 5Gb of data for £5. I doubt I'm ever going to need more than that as on a recent holiday with heavy use I didn't even get close to exceeding the usage limits.
Erm...yes? There is obviously a rush to integrate the latest generative AI tools in everything without thinking about the consequences of it's failure modes.
QEMU is always going to focus on emulation fidelity first and there are few shortcuts. With floating point the differences aren't generally in the numbers but in how the NaNs and other edge cases are handled. If you want to execute FP heavy code you should be cross compiling anyway.