public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xry111 at xry111 dot site" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/30328] New: elf/tst-cpu-features-cpuinfo fails on Athlon 64 3000+ (K8) Date: Sun, 09 Apr 2023 08:10:28 +0000 [thread overview] Message-ID: <bug-30328-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30328 Bug ID: 30328 Summary: elf/tst-cpu-features-cpuinfo fails on Athlon 64 3000+ (K8) Product: glibc Version: 2.37 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: xry111 at xry111 dot site CC: drepper.fsp at gmail dot com Target Milestone: --- The failed test is: Checking HAS_CPU_FEATURE (PREFETCHW): HAS_CPU_FEATURE (PREFETCHW): 0 cpuinfo (3dnowprefetch): 1 *** failure *** In the kernel there is: /* 3DNow or LM implies PREFETCHW */ if (!cpu_has(c, X86_FEATURE_3DNOWPREFETCH)) if (cpu_has(c, X86_FEATURE_3DNOW) || cpu_has(c, X86_FEATURE_LM)) set_cpu_cap(c, X86_FEATURE_3DNOWPREFETCH); But it seems no equivalent in Glibc. -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2023-04-09 8:10 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-30328-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).