6756768: C1 generates invalid code
Reviewed-by:

This is a day one bug with value numbering in C1. Static field
references for uninitialized classes should invalidate the memory
state but currently they allow value numbering to proceed across them.
The fix is to have LoadField and StoreField of uninitialized classes
kill memory. To get a uniform fix I extended the
ValueNumberingVisitor which describes memory effects to have a simple
subclass for use by GraphBuilder and removed the special handling in
GraphBuilder. This assures that local and global value numbering do
the same thing.

test with runthese and nsk on sparc and intel