sysudengle / rstm Goto Github PK

What steps will reproduce the problem?
1. Compile and build a 32-bit or 64-bit target with libitm2stm enabled
2. Run TreeBenchSHIM with 7 threads

What steps will reproduce the problem?
1. Perform a transaction that privatizes some locations, and then munmap the 
privatized locations non-transactionally.
2. Concurrently execute a speculative transaction that conditionally 
dereferences said locations.
3. Run for a "long time" time.

What is the expected output? 

Results consistent with single-lock semantics.

What do you see instead?

Segmentation faults from the speculative transactions due to privatization 
safety violations.

Workaround?

Perform all munmap operations inside [[relaxed]] transactions.

What steps will reproduce the problem?
1. Perform a __cancel from a nested transaction.

What is the expected output? 

Execution as-if the nested transaction had canceled.

What do you see instead?

Unpredictable results leading to failures.

Workaround?

None at the moment. `libstm` does not support closed nested transactions and 
thus we cannot support nested __cancel operations. We /do/ support 
__cancel_outer operations.

Please use labels and text to provide additional information.