[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180529123216.GA11608@andrea>
Date: Tue, 29 May 2018 14:32:16 +0200
From: Andrea Parri <andrea.parri@...rulasolutions.com>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
stern@...land.harvard.edu, will.deacon@....com,
peterz@...radead.org, boqun.feng@...il.com, npiggin@...il.com,
dhowells@...hat.com, j.alglave@....ac.uk, luc.maranget@...ia.fr,
akiyks@...il.com, mingo@...nel.org
Subject: Re: [PATCH RFC tools/memory-model] Add litmus-test naming scheme
[...]
> > 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
Powered by blists - more mailing lists