public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Umesh Kalappa <umesh.kalappa0@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Alexander Monakov <amonakov@ispras.ru>, gcc@gcc.gnu.org
Subject: Re: GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction
Date: Tue, 29 May 2018 04:20:00 -0000	[thread overview]
Message-ID: <CAGfacvRx0s0hb3pJqhkWvzUdh6hTguBmaWstRCifp5FQEKhhDw@mail.gmail.com> (raw)
In-Reply-To: <20180507083830.GF8577@tucnak>

Ok, thanks for the clarification jakub.

Umesg

On Mon, May 7, 2018, 2:08 PM Jakub Jelinek <jakub@redhat.com> wrote:

> On Mon, May 07, 2018 at 01:58:48PM +0530, Umesh Kalappa wrote:
> > CCed Jakub,
>
> > > Agree that float division don't touch memory ,but fdiv  result (stack
> > > register ) is stored  back to a memory i.e fResult .
>
> That doesn't really matter.  It is stored to a stack spill slot, something
> that doesn't have address taken and other code (e.g. in other threads)
> can't
> in a valid program access it.  That is not considered memory for the
> inline-asm, only objects that must live in memory count.
>
>         Jakub
>

  reply	other threads:[~2018-05-29  4:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07  8:28 Umesh Kalappa
2018-05-07  8:38 ` Jakub Jelinek
2018-05-29  4:20   ` Umesh Kalappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-13 12:28 Vivek Kinhekar
2018-04-13 12:34 ` Alexander Monakov
2018-04-13 12:34   ` Vivek Kinhekar
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

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=CAGfacvRx0s0hb3pJqhkWvzUdh6hTguBmaWstRCifp5FQEKhhDw@mail.gmail.com \
    --to=umesh.kalappa0@gmail.com \
    --cc=amonakov@ispras.ru \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    /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).