Paolo Carlini wrote:
I'm going to revert again the whole thing and wait for a different,
safe, approach, sorry.
In the short time frame, i.e., something solid for 4.4.0, I would
suggest two possible strategies:
1- Try to re-organize the new code in order to make possible using in
*few* selected places _GLIBCXX_ATOMIC_BUILTINS_4 to enable / disable the
new feature completely.
2- Learn from guard.cc. In that libsupc++ implementation file,
*certainly* atomic builtins are safely used, with fall-backs.
Paolo.
