From: Vivek Kinhekar <vivek.kinhekar@blackfigtech.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: RE: GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction
Date: Fri, 13 Apr 2018 12:34:00 -0000 [thread overview]
Message-ID: <MAXPR0101MB122831213432807B240E2463F0B30@MAXPR0101MB1228.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <alpine.LNX.2.20.13.1804131526260.29823@monopod.intra.ispras.ru>
Thanks for the quick response, Alexander!
Regards,
Vivek Kinhekar
+91-7709046470
-----Original Message-----
From: Alexander Monakov <amonakov@ispras.ru>
Sent: Friday, April 13, 2018 5:58 PM
To: Vivek Kinhekar <vivek.kinhekar@blackfigtech.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction
On Fri, 13 Apr 2018, Vivek Kinhekar wrote:
> The mfence instruction with memory clobber asm instruction should
> create a barrier between division and printf instructions.
No, floating-point division does not touch memory, so the asm does not (and need not) restrict its motion.
Alexander
next prev parent reply other threads:[~2018-04-13 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 12:28 Vivek Kinhekar
2018-04-13 12:34 ` Alexander Monakov
2018-04-13 12:34 ` Vivek Kinhekar [this message]
2018-04-13 13:51 ` Vivek Kinhekar
2018-04-13 16:10 ` Jakub Jelinek
2018-04-13 14:32 ` Vivek Kinhekar
2018-05-04 12:50 ` Umesh Kalappa
2018-05-07 8:28 Umesh Kalappa
2018-05-07 8:38 ` Jakub Jelinek
2018-05-29 4:20 ` Umesh Kalappa
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=MAXPR0101MB122831213432807B240E2463F0B30@MAXPR0101MB1228.INDPRD01.PROD.OUTLOOK.COM \
--to=vivek.kinhekar@blackfigtech.com \
--cc=amonakov@ispras.ru \
--cc=gcc@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).