public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/31782] New: Test build failure with recent GCC trunk (x86/tst-cpu-features-supports.c:69:3: error: parameter to builtin not valid: avx5124fmaps) Date: Tue, 21 May 2024 18:04:46 +0000 [thread overview] Message-ID: <bug-31782-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31782 Bug ID: 31782 Summary: Test build failure with recent GCC trunk (x86/tst-cpu-features-supports.c:69:3: error: parameter to builtin not valid: avx5124fmaps) Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: sam at gentoo dot org CC: carlos at redhat dot com Target Milestone: --- This broke with a recent commit in GCC trunk: commit e1a7e2c54d52d0ba374735e285b617af44841ace Author: Haochen Jiang <haochen.jiang@intel.com> Date: Mon May 20 10:43:44 2024 +0800 i386: Remove Xeon Phi ISA support -- ``` [...] ../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); | ^~~~~ ``` -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-05-21 18:04 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-21 18:04 sam at gentoo dot org [this message] 2024-05-21 18:04 ` [Bug build/31782] " sam at gentoo dot org 2024-05-21 21:00 ` hjl.tools at gmail dot com 2024-05-22 2:13 ` haochen.jiang at intel dot com 2024-05-27 19:30 ` cvs-commit at gcc dot gnu.org 2024-05-28 18:43 ` cvs-commit at gcc dot gnu.org 2024-05-28 19:54 ` cvs-commit at gcc dot gnu.org 2024-06-15 14:16 ` dilfridge at gentoo dot org 2024-06-18 8:54 ` sam at gentoo dot org
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=bug-31782-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).