From: Joseph Myers <josmyers@redhat.com>
To: libc-alpha@sourceware.org
Subject: Testsuite build failures for x86, GCC 15
Date: Thu, 23 May 2024 14:59:13 +0000 (UTC) [thread overview]
Message-ID: <e8af3db3-ce59-3bba-cf2f-6eb4d2b9224@redhat.com> (raw)
Some testsuite build failures have recently appeared on x86 with GCC
mainline:
https://sourceware.org/pipermail/libc-testresults/2024q2/012629.html
../sysdeps/x86/tst-cpu-features-supports.c: In function 'do_test':
../sysdeps/x86/tst-cpu-features-supports.c:69:3: error: parameter to builtin not valid: avx5124fmaps
69 | fails += CHECK_FEATURE_ACTIVE (avx5124fmaps, AVX512_4FMAPS);
| ^~~~~
../sysdeps/x86/tst-cpu-features-supports.c:70:3: error: parameter to builtin not valid: avx5124vnniw
70 | fails += CHECK_FEATURE_ACTIVE (avx5124vnniw, AVX512_4VNNIW);
| ^~~~~
../sysdeps/x86/tst-cpu-features-supports.c:95:3: error: parameter to builtin not valid: avx512er
95 | fails += CHECK_FEATURE_ACTIVE (avx512er, AVX512ER);
| ^~~~~
../sysdeps/x86/tst-cpu-features-supports.c:102:3: error: parameter to builtin not valid: avx512pf
102 | fails += CHECK_FEATURE_ACTIVE (avx512pf, AVX512PF);
| ^~~~~
../sysdeps/x86/tst-cpu-features-supports.c:151:3: error: parameter to builtin not valid: prefetchwt1
151 | fails += CHECK_FEATURE_ACTIVE (prefetchwt1, PREFETCHWT1);
| ^~~~~
I don't know whether this is a bug in the testsuite code or in GCC.
--
Joseph S. Myers
josmyers@redhat.com
next reply other threads:[~2024-05-23 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 14:59 Joseph Myers [this message]
2024-05-23 15:31 ` H.J. Lu
2024-05-23 23:41 ` Sunil Pandey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e8af3db3-ce59-3bba-cf2f-6eb4d2b9224@redhat.com \
--to=josmyers@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).