public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/26124] New: Export <cpu-features.h> Date: Wed, 17 Jun 2020 00:53:21 +0000 [thread overview] Message-ID: <bug-26124-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26124 Bug ID: 26124 Summary: Export <cpu-features.h> Product: glibc Version: 2.32 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com CC: drepper.fsp at gmail dot com Target Milestone: --- I got user requests to export <cpu-features.h> so that people can do #if __has_include(<cpu-features.h>) #include <cpu-features.h> #endif ... if (HAS_CPU_FEATURE (SSE3)) ... if (CPU_FEATURE_USABLE (SSE3)) ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-06-17 0:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-17 0:53 hjl.tools at gmail dot com [this message] 2020-06-17 4:46 ` [Bug libc/26124] " fweimer at redhat dot com 2020-06-17 11:36 ` hjl.tools at gmail dot com 2020-06-17 19:32 ` hjl.tools at gmail dot com 2020-09-12 15:04 ` hjl.tools at gmail 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-26124-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).