Fix a bug where memory could be corrupted during a synchronized store This is the scenario: 1. A thread performs synchronized load 2. Another thread writes to the cache line that the synchronized load was    performed from.  The load is invalidated. 3. The cache line is evicted 4. The thread performs a synchronized store to the address. This is a cache 	miss and does a read from memory. 5. The restarted synchronized store fails.   The previous logic didn't do a writeback in this case.  The problem is that   the the cache is not updated with the data that was read back from memory,   but the tags were updated as if the cache fill was performed.
Fix a bug where memory could be corrupted during a synchronized store
This is the scenario:
1. A thread performs synchronized load
2. Another thread writes to the cache line that the synchronized load was
   performed from.  The load is invalidated.
3. The cache line is evicted
4. The thread performs a synchronized store to the address. This is a cache
	miss and does a read from memory.
5. The restarted synchronized store fails.
  The previous logic didn't do a writeback in this case.  The problem is that
  the the cache is not updated with the data that was read back from memory,
  but the tags were updated as if the cache fill was performed.

The fix is to always do the writeback for a synchronized store, but to
clear the mask bits if a synchronized store failed.  This fixes
nuengine. I believe it also fixes issues with texture_c when using a barrier,
but need to retest on FPGA.

hoangt/NyuziProcessor,jbush001/NyuziProcessor,FulcronZ/NyuziProcessor,jbush001/NyuziProcessor,jbush001/NyuziProcessor,hoangt/NyuziProcessor,hoangt/NyuziProcessor,hoangt/NyuziProcessor,FulcronZ/NyuziProcessor,FulcronZ/NyuziProcessor,jbush001/NyuziProcessor,jbush001/NyuziProcessor,FulcronZ/NyuziProcessor,jbush001/NyuziProcessor