I have rewritten and adapted all the current bitfield tests that are
store data race dependent.
I am open to a better name than "memmodel". If any one has a better
idea, I'm sed competent.
I'd definately suggest something more generic which gives an indication
of whats being done... memmodel is too specific since I think it'll be
testing more than memory-model functionality now.
It invokes GDB to step through the program, looking at and/or modifying
memory every simulated cycle of a function's execution, and checking to
make sure execution proceeds as expected.
off the top of my head, maybe something like one of the following:
step-through
gdb-invoked
side-effects
simulate-thread
Or something else you can think of that is more appropriate generic name
for the types of tests.
Andrew
