* [PATCH 1/3] memorder: Fix wrong variable citation
@ 2017-09-12 0:56 SeongJae Park
2017-09-12 0:56 ` [PATCH 2/3] memorder: Remove unnecessary comma SeongJae Park
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: SeongJae Park @ 2017-09-12 0:56 UTC (permalink / raw)
To: paulmck; +Cc: perfbook, SeongJae Park
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
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
^ permalink raw reply related [flat|nested] 4+ messages in thread
* [PATCH 2/3] memorder: Remove unnecessary comma
2017-09-12 0:56 [PATCH 1/3] memorder: Fix wrong variable citation SeongJae Park
@ 2017-09-12 0:56 ` SeongJae Park
2017-09-12 0:56 ` [PATCH 3/3] future/QC: Remove unnecessary duplicate SeongJae Park
2017-09-12 3:58 ` [PATCH 1/3] memorder: Fix wrong variable citation Paul E. McKenney
2 siblings, 0 replies; 4+ messages in thread
From: SeongJae Park @ 2017-09-12 0:56 UTC (permalink / raw)
To: paulmck; +Cc: perfbook, SeongJae Park
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
memorder/memorder.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index 2da7b98..8511c3a 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -1103,7 +1103,7 @@ exists (1:r2=2 /\ 0:r2=2)
\subsubsection{Load Followed By Store}
Listing~\ref{lst:memorder:Load-Buffering Litmus Test (No Ordering)}
-(\path{C-LB+o-o+o-o.litmus}),
+(\path{C-LB+o-o+o-o.litmus})
shows the classic \emph{load-buffering} litmus test.
Although relatively strongly ordered systems such as x86
or the IBM Mainframe do not reorder prior loads with subsequent stores,
--
2.10.0
^ permalink raw reply related [flat|nested] 4+ messages in thread
* [PATCH 3/3] future/QC: Remove unnecessary duplicate
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 ` SeongJae Park
2017-09-12 3:58 ` [PATCH 1/3] memorder: Fix wrong variable citation Paul E. McKenney
2 siblings, 0 replies; 4+ messages in thread
From: SeongJae Park @ 2017-09-12 0:56 UTC (permalink / raw)
To: paulmck; +Cc: perfbook, SeongJae Park
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
future/QC.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/future/QC.tex b/future/QC.tex
index 3b01a56..e5ff74e 100644
--- a/future/QC.tex
+++ b/future/QC.tex
@@ -1016,7 +1016,7 @@ Grover's algorithm.
and $O(n \log_2 n)$ for classic-computing search?
Hash tables do $O(n)$ and $O(1)$ respectively!!!
\QuickQuizAnswer{
- Fixed-size hash table lookup lookups are $O(n)$, not $O(1)$.
+ Fixed-size hash table lookups are $O(n)$, not $O(1)$.
And for a resizing hash table, fairness dictates that the overhead
of resizing be properly accounted for.
--
2.10.0
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH 1/3] memorder: Fix wrong variable citation
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
2 siblings, 0 replies; 4+ messages in thread
From: Paul E. McKenney @ 2017-09-12 3:58 UTC (permalink / raw)
To: SeongJae Park; +Cc: perfbook
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
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-09-12 5:27 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 ` [PATCH 1/3] memorder: Fix wrong variable citation Paul E. McKenney
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox