Not sure why the 32/64 split is needed in the atomic_load
store hierarchies. The regular PatFrags do this, but we don't
do it for the existing handling for global.
I'm not 100% sure if anything else is needed to handle the different orderings correctly