public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28782] x86-64 ISA level for glibc itself is always x86-64-baseline Date: Fri, 14 Jan 2022 19:19:53 +0000 [thread overview] Message-ID: <bug-28782-131-8hJdhbkQvp@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28782-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28782 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |fweimer at redhat dot com Status|NEW |RESOLVED Target Milestone|--- |2.35 Resolution|--- |FIXED --- Comment #5 from Florian Weimer <fweimer at redhat dot com> --- First parted fixed by: commit 5732a881aad24fac876f5505a212395048a7a483 Author: Florian Weimer <fweimer@redhat.com> Date: Fri Jan 14 16:09:20 2022 +0100 x86: HAVE_X86_LAHF_SAHF, HAVE_X86_MOVBE and -march=x86-64-vN (bug 28782) HAVE_X86_LAHF_SAHF is implied by x86-64-v2, and HAVE_X86_MOVBE by x86-64-v3. The individual flag does not appear in -fverbose-asm flag output even if the ISA level implies it. Reviewed-by: H.J. Lu <hjl.tools@gmail.com> Second part fixed by: commit 990c953bce06d77360d2e933faa9a008e2c55405 Author: Florian Weimer <fweimer@redhat.com> Date: Fri Jan 14 20:16:05 2022 +0100 x86: Add x86-64-vN check to early startup This ISA level covers the glibc build itself. <dl-hwcap-check.h> cannot be used because this check (by design) happens before DL_PLATFORM_INIT and the x86 CPU flags initialization. Reviewed-by: H.J. Lu <hjl.tools@gmail.com> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-14 19:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-14 10:27 [Bug libc/28782] New: " fweimer at redhat dot com 2022-01-14 11:09 ` [Bug libc/28782] " fweimer at redhat dot com 2022-01-14 11:24 ` fweimer at redhat dot com 2022-01-14 12:20 ` fweimer at redhat dot com 2022-01-14 12:45 ` fweimer at redhat dot com 2022-01-14 19:19 ` fweimer at redhat dot com [this message] 2023-08-16 6:41 ` 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-28782-131-8hJdhbkQvp@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).