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/99704] New: volatile is needed on asm statements in <cpuid.h> Date: Mon, 22 Mar 2021 02:37:51 +0000 [thread overview] Message-ID: <bug-99704-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99704 Bug ID: 99704 Summary: volatile is needed on asm statements in <cpuid.h> Product: gcc Version: 9.3.1 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, ubizjak at gmail dot com Target Milestone: --- Target: i386,x86-64 Since CPUID instruction may return different values on hybrid core. volatile is needed on asm statements in <cpuid.h>.
next reply other threads:[~2021-03-22 2:37 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-22 2:37 hjl.tools at gmail dot com [this message] 2021-03-22 2:50 ` [Bug target/99704] " hjl.tools at gmail dot com 2021-03-22 4:58 ` crazylht at gmail dot com 2021-03-22 7:11 ` crazylht at gmail dot com 2021-03-23 12:26 ` cvs-commit at gcc dot gnu.org 2021-03-23 12:40 ` cvs-commit at gcc dot gnu.org 2021-03-23 12:51 ` cvs-commit at gcc dot gnu.org 2021-03-23 12:53 ` cvs-commit at gcc dot gnu.org 2021-03-23 12:54 ` 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-99704-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: 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).