> <
http://checkfence.sourceforge.net/>
www.cis.upenn.edu/~alur/Talks/milner08.ppt
>
> <
http://www.cis.upenn.edu/~alur/Talks/milner08.ppt>
www.cis.upenn.edu/~alur/Talks/ucla07.ppt
>
>
www.cis.upenn.edu/acg/talks/pldi07_
> <goog_1260407957268>*checkfence<goog_1260407957268>
> *_talk.ppt </>
[I guess this one must go to the Relacy group, so I cc it.]
Hi Kimo,
Yes, I had researched CheckFence a bit before started work on Relacy.
The main two things that forced me to turn away from CheckFence are:
1. It supports only limited subset of C language. And what I want to
verify is production C/C++ with all these templates, unions,
externally compiled code, thread-local storage, dynamic thread
creation, various OS APIs and whatever.
2. Memory model supported by CheckFence is *very* limited. They only
support atomic operations (I guess fully sequentially consistent) and
4 types of fences. I identified that as "not enough" for real-life
development. Once can't model neither C++0x memory model nor most of
the hardware memory models with it.
--
Dmitriy V'jukov