From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 1/3] memorder: Fix wrong variable citation
Date: Mon, 11 Sep 2017 20:58:49 -0700 [thread overview]
Message-ID: <20170912035849.GR3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170912005617.19975-1-sj38.park@gmail.com>
On Tue, Sep 12, 2017 at 09:56:15AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Good eyes! Applied all three, thank you!
Thanx, Paul
> ---
> memorder/memorder.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/memorder/memorder.tex b/memorder/memorder.tex
> index 183c525..2da7b98 100644
> --- a/memorder/memorder.tex
> +++ b/memorder/memorder.tex
> @@ -704,8 +704,8 @@ as Y0, the store to \co{x1} on line~19 as Y1, and the load from
> Applying the if-then rule step by step, we know that the store to
> \co{x1} on line~19 happens after the load from \co{x1} on line~11 if
> \co{P0()}'s local variable \co{r2} is set to the value zero.
> -The if-then rule would then state that the load from \co{x1} on
> -line~21 happens after the store to \co{x1} on line~9.
> +The if-then rule would then state that the load from \co{x0} on
> +line~21 happens after the store to \co{x0} on line~9.
> In other words,
> \co{P1()}'s local variable \co{r2} is guaranteed
> to end up with the value two \emph{only if}
> --
> 2.10.0
>
prev parent reply other threads:[~2017-09-12 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 0:56 [PATCH 1/3] memorder: Fix wrong variable citation SeongJae Park
2017-09-12 0:56 ` [PATCH 2/3] memorder: Remove unnecessary comma SeongJae Park
2017-09-12 0:56 ` [PATCH 3/3] future/QC: Remove unnecessary duplicate SeongJae Park
2017-09-12 3:58 ` Paul E. McKenney [this message]
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=20170912035849.GR3521@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.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