Skip to content

Comment on GCC 4.7 adds transactional memory extensions for C/C++

Comments

This is pretty cool. Is it done naively and using one global lock, or is it be more intelligent? Can GCC identify what memory location require locking for a given transaction, and lock just those? What is the granularity?

It's smarter than a global lock (come on!). I would suggest reading the article which describes the implementation [1].

[1]: http://www.velox-project.eu/velox-transactional-memory-stack (courtesy scott_s)

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.