public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arthur200126 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/23249] Epyc and other current AMD CPUs do not select the "haswell" platform subdirectory Date: Sun, 10 May 2020 00:41:46 +0000 [thread overview] Message-ID: <bug-23249-131-qkf8WDBuV6@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-23249-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=23249 --- Comment #11 from Mingye Wang <arthur200126 at gmail dot com> --- I agree that a "generational" revision scheme would be helpful in the long run. For that information we can consult compiler databases (gcc/gcc/common/config/i386/i386-common.c + gcc/config/i386/i386.h or llvm/clang/include/clang/Basic/X86Target.def) and make some sort of table to work with. The LLVM project's version seems to already imply a generational scheme, although they appear to be taking a lot of liberties by eliding a lot of the stuff they don't use. They also don't seem to care about less-used stuff like VIA. The GCC database does include the VIA CPUs, but the part about eden-x4 not having any sort of AVX is a bit dubious. Hell, their documentation mentions it having AVX2... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-10 0:41 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23249-131@http.sourceware.org/bugzilla/> 2020-04-22 15:41 ` fweimer at redhat dot com 2020-04-22 15:41 ` fweimer at redhat dot com 2020-05-05 7:02 ` david.abdurachmanov at gmail dot com 2020-05-08 18:43 ` fweimer at redhat dot com 2020-05-10 0:41 ` arthur200126 at gmail dot com [this message] 2020-06-24 21:55 ` tcl_de at gmx dot net 2020-06-26 15:27 ` arthur200126 at gmail dot com 2020-06-26 19:29 ` tcl_de at gmx dot net 2020-08-31 5:03 ` arthur200126 at gmail dot com 2020-08-31 13:13 ` fweimer at redhat dot com 2020-12-04 8:50 ` fweimer at redhat dot com 2021-01-03 19:19 ` josephriches at gmail dot com 2021-01-04 8:02 ` fweimer at redhat dot com 2021-01-05 19:27 ` josephriches at gmail dot com 2021-01-05 20:03 ` fweimer at redhat dot com
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-23249-131-qkf8WDBuV6@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).