aboutsummaryrefslogtreecommitdiff
path: root/libjava/gnu/xml/dom/DomDocumentBuilder.h
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2025-09-02 17:01:30 +0200
committerJakub Jelinek <jakub@gcc.gnu.org>2025-09-02 17:02:52 +0200
commita41d8edf304e896cb541a0ec7daafb02b8d442c7 (patch)
tree63e66c4d6c7bfe6ce8b200216fe776b7cfecb9ba /libjava/gnu/xml/dom/DomDocumentBuilder.h
parentff9e44ee3189d24127bc754a8563be4615239730 (diff)
downloadgcc-a41d8edf304e896cb541a0ec7daafb02b8d442c7.zip
gcc-a41d8edf304e896cb541a0ec7daafb02b8d442c7.tar.gz
gcc-a41d8edf304e896cb541a0ec7daafb02b8d442c7.tar.bz2
s390: Adjust s390/spaceship-fp-*.c tests for recent changes
In r16-3414 libstdc++ changed ABI for (still experimental C++20) and uses unordered value -128 instead of 2. Generally the change improved code generation on all targets tested, see https://gcc.gnu.org/pipermail/gcc-patches/2025-August/693534.html for details. In r16-3474 I've adjusted the middle-end and backends to use that value. This apparently broke the gcc.target/s390/spaceship-fp-2.c test, with -ffast-math the 2 value is unreachable and so the .SPACESHIP last argument in that case is the default, which changed from 2 to -128. But spaceship-fp-1.c test also doesn't test what libstdc++ uses anymore, so the following patch uses -128 in all the spots. 2025-09-02 Jakub Jelinek <jakub@redhat.com> * gcc.target/s390/spaceship-fp-1.c: Expect .SPACESHIP call with -128 as last argument instead of 2. (TEST): Use -128 instead of 2. * gcc.target/s390/spaceship-fp-2.c: Expect .SPACESHIP call with -128 as last argument instead of 2. (TEST): Use -128 instead of 2.
Diffstat (limited to 'libjava/gnu/xml/dom/DomDocumentBuilder.h')
0 files changed, 0 insertions, 0 deletions