public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99704] volatile is needed on asm statements in <cpuid.h> Date: Tue, 23 Mar 2021 12:53:00 +0000 [thread overview] Message-ID: <bug-99704-4-o37fA6ryeZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99704-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99704 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-8 branch has been updated by H.J. Lu <hjl@gcc.gnu.org>: https://gcc.gnu.org/g:3553e057df3a7fb2524339b1681fe3153ae7d568 commit r8-10816-g3553e057df3a7fb2524339b1681fe3153ae7d568 Author: H.J. Lu <hjl.tools@gmail.com> Date: Sun Mar 21 19:47:24 2021 -0700 x86: Add __volatile__ to __cpuid and __cpuid_count Since CPUID instruction may return different values on hybrid core. volatile is needed on asm statements in <cpuid.h>. PR target/99704 * config/i386/cpuid.h (__cpuid): Add __volatile__. (__cpuid_count): Likewise. (cherry picked from commit 9c89c9e9c6b59260c7745c8714b69f94784a9c13)
next prev parent reply other threads:[~2021-03-23 12:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-22 2:37 [Bug target/99704] New: " hjl.tools at gmail dot com 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 [this message] 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-o37fA6ryeZ@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).