public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95973] New: Add __cpuidex
Date: Mon, 29 Jun 2020 16:31:48 +0000 [thread overview]
Message-ID: <bug-95973-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95973
Bug ID: 95973
Summary: Add __cpuidex
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: crazylht at gmail dot com, wwwhhhyyy333 at gmail dot com
Target Milestone: ---
Target: i386, x86-64
GCC has
__cpuid_count(leaf,subleaf, a,b,c,d)
MSVS has
void __cpuidex(
int cpuInfo[4],
int function_id,
int subfunction_id
);
MSVS's interface is a little more sensible, passing & returning an array vs
modifying 4 arguments in an un-C-language-like way. We should add __cpuidex.
next reply other threads:[~2020-06-29 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 16:31 hjl.tools at gmail dot com [this message]
2020-07-18 11:53 ` [Bug target/95973] " hjl.tools at gmail dot com
2020-07-19 11:21 ` cvs-commit at gcc dot gnu.org
2020-07-19 12:26 ` 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-95973-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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: link
Be 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).