* Added XMU Settings to the Input Screen
* Added Peripherals to config
* Prevent overwriting existing XMUs
* Added blockdev.h to try to fix the MacOS build
* Fixed some issues that antangelo pointed out
* Moved the peripheralType and param vars into the loop
* Moved fatx.h and fatx.c to ui\thirdparty\fatx
* Added Validation for Peripheral Settings
* Fixed some nits that were pointed out
* don't pass NULL into xemu_settings_set_string
* Changes following Matt's recommendations
* Changes to XMU FilePicker
* XMU image auto-bind logic refactor
* renamed peripheralType to peripheral_type
* removed unnecessary calls to g_strdup_printf and g_free
* Cleaned up some comments, removed an unnecessary variable
* handle overwrite prompt in Windows
* Fixed some code format and style inconsistencies
* More formatting fixes
* Fixed a few memory leaks
* qemu_access: check for Read and Write access
* Run clang-format
* Remove unused xemu_new_xmu declaration
* Fix use after free in rebind code
* rebase code
* remove unsused item
* restore "system" displaying on first boot
* restore popup menu functions (separate commit)
* restore snapshot function in popup menu
* get current index value from config file
Compared to other SSE instructions, VUCOMISx and VCOMISx are different:
the single and double precision versions are distinguished through a
prefix, however they use no-prefix and 0x66 for SS and SD respectively.
Scalar values usually are associated with 0xF2 and 0xF3.
Because of these, they incorrectly perform a 128-bit memory load instead
of a 32- or 64-bit load. Fix this by writing a custom decoding function.
I tested that the reproducer is fixed and the test-avx output does not
change.
Reported-by: Gabriele Svelto <gsvelto@mozilla.com>
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1637
Fixes: f8d19eec0d ("target/i386: reimplement 0x0f 0x28-0x2f, add AVX", 2022-10-18)
Cc: qemu-stable@nongnu.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>