https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124288
--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <[email protected]>: https://gcc.gnu.org/g:fd0f08443955410179d1b06c80bc5a3331d2916d commit r16-7848-gfd0f08443955410179d1b06c80bc5a3331d2916d Author: Jakub Jelinek <[email protected]> Date: Mon Mar 2 15:44:40 2026 +0100 testsuite: Fix up vec-cvt-1.c for excess precision target [PR124288] The intent of the code is to find the largest (or smallest) representable float (or double) smaller (or greater than) or equal to the given integral maximum (or minimum). The code uses volatile vars to avoid excess precision, but was relying on (volatile_var1 = something1 - something2) == volatile_var2 to actually store the subtraction into volatile var and read it from there, making it an optimization barrier. That is not the case, we compare directly the rhs of the assignment expression with volatile_var2, so on excess precision targets it can result in unwanted optimizations. Fixed by using a comma expression to make sure comparison doesn't know the value to compare. 2026-03-02 Jakub Jelinek <[email protected]> PR tree-optimization/124288 * gcc.dg/torture/vec-cvt-1.c (FLTTEST): Use comma expression to store into {flt,dbl}m{in,ax} and read from it again for comparison.
