From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
stern@rowland.harvard.edu, will.deacon@arm.com,
peterz@infradead.org, boqun.feng@gmail.com, npiggin@gmail.com,
dhowells@redhat.com, j.alglave@ucl.ac.uk, luc.maranget@inria.fr,
akiyks@gmail.com, mingo@kernel.org
Subject: Re: [PATCH RFC tools/memory-model] Add litmus-test naming scheme
Date: Tue, 29 May 2018 14:32:16 +0200 [thread overview]
Message-ID: <20180529123216.GA11608@andrea> (raw)
In-Reply-To: <20180529121941.GG3803@linux.vnet.ibm.com>
[...]
> > Right, thanks. Ah, maybe we should strive to meet the 80-chars bound
> > by splitting the command with "\"?
>
> We could, but combined with your later request for indentation, we end
> up with something like this:
>
> $ norm7 -bell linux-kernel.bell \
> Rfi Once PodRR Once Fre Once Rfi Once PodRR Once Fre Once | \
> sed -e 's/:.*//g'
> SB+rfionceonce-poonceonces
>
> In the immortal words of MSDOS, are you sure? ;-)
I find it more readable, but it's just taste ;-) Commands are indented
with 2 spaces in the other README.
> > Well, "Rfi" produces "rfi" while "PosWR" produces "pos" for a name...
>
> Right you are! How about this, then?
>
> Rfi: Read-from internal. The current process wrote a variable and then
> immediately read the value back from it. For the purposes of
> litmus-test code generation, Rfi acts identically to PosWR.
> However, they differ for purposes of naming, and they also result
> in different "exists" clauses.
> Example: ???
LGTM, thanks.
Andrea
next prev parent reply other threads:[~2018-05-29 12:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 19:10 [PATCH RFC tools/memory-model] Add litmus-test naming scheme Paul E. McKenney
2018-05-28 11:20 ` Andrea Parri
2018-05-28 21:48 ` Paul E. McKenney
2018-05-28 21:48 ` Paul E. McKenney
2018-05-28 21:48 ` Paul E. McKenney
2018-05-29 9:33 ` Andrea Parri
2018-05-29 12:19 ` Paul E. McKenney
2018-05-29 12:19 ` Paul E. McKenney
2018-05-29 12:19 ` Paul E. McKenney
2018-05-29 12:32 ` Andrea Parri [this message]
2018-05-29 9:30 ` Will Deacon
2018-05-29 12:11 ` Paul E. McKenney
2018-05-29 20:17 ` Will Deacon
2018-09-06 0:01 ` Paul E. McKenney
2018-09-06 13:52 ` Will Deacon
2018-09-06 15:13 ` Paul E. McKenney
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=20180529123216.GA11608@andrea \
--to=andrea.parri@amarulasolutions.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.