search for: nontransactionally

...en be linked and LTO'd, so there's no noticeable performance difference to directly transforming loads/stores to HTM transactional loads/stores. However, this might not be the case for each HTM. For example, transactionally accessed variables on the stack might have to be separated from nontransactionally accesses stack slots if they are on the same cache line, or the compiler has to detect this an instruct the TM to use STM instead of HTM. Torvald

...t; LTO'd, so there's no noticeable performance difference to directly transforming > loads/stores to HTM transactional loads/stores. However, this might not be the > case for each HTM. For example, transactionally accessed variables on the > stack might have to be separated from nontransactionally accesses stack slots > if they are on the same cache line, or the compiler has to detect this an > instruct the TM to use STM instead of HTM. > > > Torvald > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu h...

Hi Torvald, > I would like to know whether the community is interested in getting support > for Transactional Memory (TM) merged in upstream LLVM. I guess not :( TM basically gives you > transaction properties (eg, virtually atomic + isolated execution) for > ordinary program code. Thus, to make incrementing a counter thread-safe, you > could say __transaction { counter++; } and

Hi, I would like to know whether the community is interested in getting support for Transactional Memory (TM) merged in upstream LLVM. TM basically gives you transaction properties (eg, virtually atomic + isolated execution) for ordinary program code. Thus, to make incrementing a counter thread-safe, you could say __transaction { counter++; } and the compiler would transform this code so