[r14-2786 Regression] FAIL: g++.target/i386/pr98218-1.C -std=gnu++98 scan-assembler-times cmpltps 3 on Linux/x86_64

[r14-2786 Regression] FAIL: g++.target/i386/pr98218-1.C -std=gnu++98 scan-assembler-times cmpltps 3 on Linux/x86_64

[haochen.jiang]

On Linux/x86_64,

ade30fad6669e5f34ca4c587c724d74ecc953175 is the first bad commit
commit ade30fad6669e5f34ca4c587c724d74ecc953175
Author: Uros Bizjak <ubizjak@gmail.com>
Date:   Wed Jul 26 11:10:46 2023 +0200

    i386: Clear upper half of XMM register for V2SFmode operations [PR110762]

caused

FAIL: gcc.target/i386/pr106910-1.c scan-assembler-times roundps 9
FAIL: g++.target/i386/pr98218-1.C  -std=gnu++14  scan-assembler-times cmpltps 3
FAIL: g++.target/i386/pr98218-1.C  -std=gnu++14  scan-assembler-times pcmpgtd 2
FAIL: g++.target/i386/pr98218-1.C  -std=gnu++17  scan-assembler-times cmpltps 3
FAIL: g++.target/i386/pr98218-1.C  -std=gnu++17  scan-assembler-times pcmpgtd 2
FAIL: g++.target/i386/pr98218-1.C  -std=gnu++20  scan-assembler-times cmpltps 3
FAIL: g++.target/i386/pr98218-1.C  -std=gnu++20  scan-assembler-times pcmpgtd 2
FAIL: g++.target/i386/pr98218-1.C  -std=gnu++98  scan-assembler-times cmpltps 3
FAIL: g++.target/i386/pr98218-1.C  -std=gnu++98  scan-assembler-times pcmpgtd 2

with GCC configured with

../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-2786/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap

To reproduce:

$ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr106910-1.c --target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=g++.target/i386/pr98218-1.C --target_board='unix{-m64\ -march=cascadelake}'"

(Please do not reply to this email, for question about this report, contact me at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command line might save that.)
(However, please make sure that there is no potential problems with AVX512.)