From f1be76b0fb0eefe52864448377df62c81fd9a3e1 Mon Sep 17 00:00:00 2001 From: Brian Norris Date: Tue, 4 Jun 2013 16:30:00 -0700 Subject: [PATCH 1/1] README: a few more formatting issues --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 218e960..23492eb 100644 --- a/README.md +++ b/README.md @@ -166,8 +166,8 @@ The following list describes each of the columns in the execution trace output: * Action type: The type of operation performed - * MO: The memory-order for this operation (i.e., `memory_order_XXX`, where XXX is - relaxed, release, acquire, rel_acq, or seq_cst) + * MO: The memory-order for this operation (i.e., `memory_order_XXX`, where `XXX` is + `relaxed`, `release`, `acquire`, `rel_acq`, or `seq_cst`) * Location: The memory location on which this operation is operating. This is well-defined for atomic write/read/RMW, but other operations are subject to @@ -176,7 +176,7 @@ The following list describes each of the columns in the execution trace output: * Value: For reads/writes/RMW, the value returned by the operation. Note that for RMW, this is the value that is *read*, not the value that was *written*. For other operations, 'value' may have some CDSChecker-internal meaning, or - it may simply be a don't-care (such as 0xdeadbeef). + it may simply be a don't-care (such as `0xdeadbeef`). * Rf: For reads, the sequence number of the operation from which it reads. [Note: If the execution is a partial, infeasible trace (labeled INFEASIBLE), -- 2.34.1