[csmith-dev] testing C++11 struct rules

[Xuejun Yang]

Yes, I will think about it. None of the initial solutions came to my mind
seems to be trivial.

-Xuejun

-----Original Message-----
From: csmith-dev-bounces at flux.utah.edu
[mailto:csmith-dev-bounces at flux.utah.edu] On Behalf Of John Regehr
Sent: Sunday, May 13, 2012 8:05 AM
To: csmith-dev at flux.utah.edu
Subject: Re: [csmith-dev] testing C++11 struct rules

My main goal is to catch races introduced by the compiler.

The last time I checked (in Dec) G++ would introduce races on struct fields
even when given all of the C++ memory model flags.  I suspect it's going to
take them some time to iron out all of the latent incompatibilities between
GCC and the new memory model, and my thought was that random testing could
accelerate that process.

Xuejun, your static information about field accesses is going to be rather
pessimistic.  This might be OK for bug-finding, but it'll make it less
effective.  Can you think of any non-pessimistic way (dynamic, I
mean) to figure out which struct fields are touched by a random program?

John