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/31867] "CPU ISA level is lower than required" on SSE2-free CPUs Date: Sun, 09 Jun 2024 08:39:54 +0000 [thread overview] Message-ID: <bug-31867-131-pRwVevoBcO@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31867-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31867 --- Comment #1 from Sam James <sam at gentoo dot org> --- In sysdeps/x86/isa-level.h, we correctly do: ``` #if defined __SSE__ && defined __SSE2__ /* NB: ISAs, excluding MMX, in x86-64 ISA level baseline are used. */ # define __X86_ISA_V1 1 #else # define __X86_ISA_V1 0 #endif ``` But when we run the configure test, we do... ``` cat > conftest.c <<EOF #include <sysdeps/x86/isa-level.h> #if MINIMUM_X86_ISA_LEVEL >= 4 libc_cv_have_x86_isa_level=4 #elif MINIMUM_X86_ISA_LEVEL == 3 libc_cv_have_x86_isa_level=3 #elif MINIMUM_X86_ISA_LEVEL == 2 libc_cv_have_x86_isa_level=2 #else libc_cv_have_x86_isa_level=baseline #endif EOF ``` On a CPU without SSE2, we will get 'baseline', and then... ``` if test $libc_cv_have_x86_isa_level = baseline; then AC_DEFINE_UNQUOTED(MINIMUM_X86_ISA_LEVEL, 1) else AC_DEFINE_UNQUOTED(MINIMUM_X86_ISA_LEVEL, $libc_cv_have_x86_isa_level) fi ``` We set MINIMUM_X86_ISA_LEVEL to 1, not 0, which seems wrong. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-09 8:39 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-09 8:36 [Bug build/31867] New: " sam at gentoo dot org 2024-06-09 8:36 ` [Bug build/31867] " sam at gentoo dot org 2024-06-09 8:36 ` sam at gentoo dot org 2024-06-09 8:39 ` sam at gentoo dot org [this message] 2024-06-09 9:41 ` sam at gentoo dot org 2024-06-09 9:50 ` sam at gentoo dot org 2024-06-09 10:46 ` hjl.tools at gmail dot com 2024-06-09 13:44 ` sam at gentoo dot org 2024-06-09 13:53 ` sam at gentoo dot org 2024-06-09 20:50 ` hjl.tools at gmail dot com 2024-06-09 20:52 ` hjl.tools at gmail dot com 2024-06-10 16:46 ` sam at gentoo dot org 2024-06-11 7:10 ` cvs-commit at gcc dot gnu.org 2024-06-11 23:24 ` sam at gentoo dot org 2024-06-11 23:28 ` sam at gentoo dot org 2024-06-12 4:06 ` sam at gentoo dot org 2024-06-14 4:08 ` sam at gentoo dot org 2024-06-14 4:08 ` sam at gentoo dot org 2024-06-15 10:14 ` cvs-commit at gcc dot gnu.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-31867-131-pRwVevoBcO@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).