x86 testsuite: Specify generic tuning on more tests
More x86 test cases now explicitly use generic tuning to ensure consistent behavior.
Numerous x86 test cases have been updated to explicitly specify generic tuning using the -mtune=generic flag. This change addresses issues where tests fail when compiled with non-default CPU or tuning settings, typically because they rely on specific code generation patterns observed with generic tuning. By ensuring these tests run with generic tuning, their behavior becomes predictable and consistent, preventing failures related to specialized microarchitecture optimizations.
In Details
This commit adds -mtune=generic to a number of i386 test cases in the GCC testsuite. The rationale is that these tests perform scanasm or body scan operations that expect code generated under 'generic' tuning. When compiled with specific CPU tuning (e.g., -march=native or a particular CPU model), the generated assembly might differ from what the tests expect, leading to failures. Explicitly setting -mtune=generic ensures that these tests validate code generation against a stable baseline, independent of the host's or build system's specific CPU configuration.
- generic tuning
- A broad tuning strategy in GCC that aims for good performance across a wide range of processors, rather than optimizing for a specific microarchitecture.
- scanasm
- A testing technique that involves scanning generated assembly code for specific patterns or instructions.
- CPU tuning
- The process of optimizing compiler output for the specific characteristics and instruction set extensions of a particular processor model or microarchitecture.