This is pretty cool. Is it done naively and using one global lock, or is it be m... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

CGamesPlay on Nov 21, 2011 | parent | context | favorite | on: GCC 4.7 adds transactional memory extensions for C...

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?

roxtar on Nov 22, 2011 [–]

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)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact