JDK-8140309 introduced the notion of unaligned and mismatched stores/loads. GraphKit::make_load()/store_to_memory() and IdealKit::load()/store() should be improved to use a bitmask instead of three boolean fields.
Comments
John wrote:
"It looks good to me, too, but I'm not fully comfortable with three booleans in a row.
The API is starting to look like a Turing Tape. Let's file a cleanup bug on it,
to collapse those three booleans into a single bitmask, with named components,
something like LoadNode::ControlDependency. (MemNode::Mismatch=4, etc.)
More substantively, Panama will eventually make mismatched accesses very
common, as we overlay C-like data structures inside of byte[] and long[] carriers,
or inside flat carrier objects (e.g., Long4 with fields long c0,c1,c2,c3).
Have we got a robust solution to keep the memory references straight,
when we are using C-like viewing casts on carrier bits?"