From: "Winfried Magerl" <winfried.magerl@t-online.de>
To: libc-alpha@sourceware.org
Subject: AMD 3900X: FAIL: elf/tst-cpu-features-cpuinfo
Date: Sat, 30 Jan 2021 09:34:56 +0100 [thread overview]
Message-ID: <YBUaMLEeXCjG/hvI@winnix.dyndns.org> (raw)
Hello,
I got a suspicious error when building current upcoming glibc-2.33:
FAIL: elf/tst-cpu-features-cpuinfo
The relavant details from elf/tst-cpu-features-cpuinfo.out
(likely invariant_tsc can be ignored):
Checking HAS_CPU_FEATURE (INVARIANT_TSC):
HAS_CPU_FEATURE (INVARIANT_TSC): 1
cpuinfo (invariant_tsc): 0
*** missing in /proc/cpuinfo ***
Checking HAS_CPU_FEATURE (SSBD):
HAS_CPU_FEATURE (SSBD): 0
cpuinfo (ssbd): 1
*** failure ***
Checking HAS_CPU_FEATURE (STIBP):
HAS_CPU_FEATURE (STIBP): 0
cpuinfo (stibp): 1
*** failure ***
2 differences between /proc/cpuinfo and glibc code.
The details of the build-system:
cpu: AMD Ryzen 9 3900X 12-Core Processor
os: openSUSE Tumbleweed 20210128
gcc: gcc-10-3.1.x86_64
binutils: binutils-2.35.1-1.1
Maybe this helps to track down the problem. From a quick look it's
likely uncritical because the feature is simply missing (as opposed
to a missdetected non-existing feature).
regards
winfried
next reply other threads:[~2021-01-30 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 8:34 Winfried Magerl [this message]
2021-01-30 10:16 ` Winfried Magerl
2021-01-30 13:59 ` [PATCH] x86: Check SSBD and STIBP only on Intel CPUs H.J. Lu
2021-01-30 16:26 ` Winfried Magerl
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=YBUaMLEeXCjG/hvI@winnix.dyndns.org \
--to=winfried.magerl@t-online.de \
--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).