public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56027] ldmxcsr permuted with asm Date: Fri, 18 Jan 2013 12:09:00 -0000 [thread overview] Message-ID: <bug-56027-4-NQi2A731Wo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56027-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56027 --- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> 2013-01-18 12:08:52 UTC --- (In reply to comment #3) > > I am mostly wondering what guarantees I have there won't be re-ordering. *mxcsr > > are unspec_volatile and thus can commute with asm (register) but not asm > > volatile or asm (memory in V1)? And function calls (fesetenv in V2) can't > > commute with regular asm, volatile isn't required there? > > You always need volatile here, even if in practice it seems that it is > not required for a function call. volatile tells it that the asm is > a scheduling barrier for other volatile instructions. Thanks, I'll do that. > So - it works for you then and we can close this bug? Give me a few hours, I'll close it this afternoon or tomorrow unless I come up with a reason not to. I probably should have asked on gcc-help instead of opening a PR.
next prev parent reply other threads:[~2013-01-18 12:09 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-18 10:24 [Bug target/56027] New: " glisse at gcc dot gnu.org 2013-01-18 10:46 ` [Bug target/56027] " rguenth at gcc dot gnu.org 2013-01-18 11:15 ` glisse at gcc dot gnu.org 2013-01-18 11:49 ` rguenth at gcc dot gnu.org 2013-01-18 12:09 ` glisse at gcc dot gnu.org [this message] 2013-01-18 15:33 ` glisse at gcc dot gnu.org
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-56027-4-NQi2A731Wo@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).