search for: 0x0000abcd

...ad 0x1234ABCD after we're done. NOTE: The two starred instructions (the store for s1 and the load for s2) *must* be executed in that order. Otherwise, the s2 read-modify-write will see the old value of s1, and will clobber it when it writes back (yielding an incorrect mem[0x1000] value of 0x0000ABCD). I'm not experienced enough with LLVM to figure out the most precise way to express this dependence in my lowering function. My current solution is to mark all loads and stores in these cases as volatile. This is too heavy-handed for my taste, and disallows reordering loads and stores t...