From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>,
Libc-stable Mailing List <libc-stable@sourceware.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] x86: tst-cpu-features-supports.c: Update AMX check
Date: Thu, 22 Apr 2021 10:08:57 -0700 [thread overview]
Message-ID: <CAMe9rOpF7gUfRZ6irUevHOXoHPGeXB_Q2_2Uww+3qmj_3WD=EA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2104221707070.422054@digraph.polyomino.org.uk>
On Thu, Apr 22, 2021 at 10:08 AM Joseph Myers <joseph@codesourcery.com> wrote:
>
> On Wed, 21 Apr 2021, H.J. Lu via Libc-alpha wrote:
>
> > On Wed, Apr 21, 2021 at 3:45 PM Joseph Myers <joseph@codesourcery.com> wrote:
> > >
> > > 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).
> > >
> >
> > Try this.
>
> That patch fixes the build failures for me.
>
> (Note: the fix ought to go on 2.33 branch as well, otherwise that branch
> will fail to build the testsuite with GCC 11.1 release.)
I will check it into master branch and backport it to 2.33 branch.
Thanks.
--
H.J.
parent reply other threads:[~2021-04-22 17:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.DEB.2.22.394.2104221707070.422054@digraph.polyomino.org.uk>]
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='CAMe9rOpF7gUfRZ6irUevHOXoHPGeXB_Q2_2Uww+3qmj_3WD=EA@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-stable@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).