This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

SSA Operands Locking


Greetings,

After looking through the manual there seem to be a number of for iterating marcos related to PHI or SSA nodes. Since iterating through nodes is shared state I was wondering whether we should lock internal to the marco itself around the iteration or around each caller of one of these marcos and just update the manual to warn about that in terms of implementing Multi-Threading. It doesn't really matter in terms of technical functionality but should we assume that developers will remember to lock a mutex around these iteration marcos for SSA or PHI nodes.


Not sure about the status of C++11 but when it gets merged we can just lock this using std::mutex,

Nick



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]