On Mon, Oct 05, 2020 at 11:53:10AM -0400, Alan Stern wrote:
> On Mon, Oct 05, 2020 at 05:15:57PM +0200, Luc Maranget wrote:
> > > On Sun, Oct 04, 2020 at 12:16:31AM +0900, Akira Yokosawa wrote:
> > > > > P1(int *x, int *y)
> > > > > {
> > > > > WRITE_ONCE(*x, READ_ONCE(*y));
> > > >
> > > > Looks like this one-liner doesn't provide data-dependency of y -> x on herd7.
> > >
> > > You're right. This is definitely a bug in herd7.
> > >
> > > Luc, were you aware of this?
> >
> > Hi Alan,
> >
> > No I was not aware of it. Now I am, the bug is normally fixed in the master branch of herd git deposit.
> > <https://github.com/herd/herdtools7/commit/0f3f8188a326d5816a82fb9970fcd209a2678859>
> >
> > Thanks for the report.
>
> I tested the new commit -- it does indeed fix the problem.
Beat me to it, very good! ;-)
But were you using the crypto-control-data litmus test? That one still
gets me Sometimes:
$ herd7 -version
7.56+02~dev, Rev: 0f3f8188a326d5816a82fb9970fcd209a2678859
$ herd7 -conf linux-kernel.cfg ~/paper/scalability/LWNLinuxMM/litmus/manual/kernel/crypto-control-data.litmus
Test crypto-control-data Allowed
States 2
0:r1=0;
0:r1=1;
Ok
Witnesses
Positive: 1 Negative: 4
Condition exists (0:r1=1)
Observation crypto-control-data Sometimes 1 4
Time crypto-control-data 0.00
Hash=10898119bac87e11f31dc22bbb7efe17
Or did I mess something up?
Thanx, Paul
