From: Joseph Myers <joseph@codesourcery.com>
To: <libc-alpha@sourceware.org>
Subject: tst-cpu-features-supports.c build failures
Date: Wed, 21 Apr 2021 20:52:41 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2104212049390.368224@digraph.polyomino.org.uk> (raw)
With GCC mainline, I'm seeing glibc testsuite build failures for x86_64
and x86:
../sysdeps/x86/tst-cpu-features-supports.c: In function 'do_test':
../sysdeps/x86/tst-cpu-features-supports.c:62:3: error: parameter to builtin not valid: amx_bf16
62 | fails += CHECK_SUPPORTS (amx_bf16, AMX_BF16);
| ^~~~~
../sysdeps/x86/tst-cpu-features-supports.c:63:3: error: parameter to builtin not valid: amx_int8
63 | fails += CHECK_SUPPORTS (amx_int8, AMX_INT8);
| ^~~~~
../sysdeps/x86/tst-cpu-features-supports.c:64:3: error: parameter to builtin not valid: amx_tile
64 | fails += CHECK_SUPPORTS (amx_tile, AMX_TILE);
| ^~~~~
https://sourceware.org/pipermail/libc-testresults/2021q2/007827.html
The code in question is inside a conditional
#if __GNUC_PREREQ (11, 1)
so wasn't compiled until the GCC version number was increased to 12 (and
would probably start failing with GCC 11 branch as soon as 11.1 is
released).
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2021-04-21 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 20:52 Joseph Myers [this message]
2021-04-22 1:43 ` [PATCH] x86: tst-cpu-features-supports.c: Update AMX check H.J. Lu
2021-04-22 17:07 ` Joseph Myers
2021-04-22 17:08 ` H.J. Lu
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=alpine.DEB.2.22.394.2104212049390.368224@digraph.polyomino.org.uk \
--to=joseph@codesourcery.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).