https://bugs.kde.org/show_bug.cgi?id=369459
--- Comment #9 from Julian Seward <jsew...@acm.org> --- Maybe we could use Maran's proposal for fixing the same problem on MIPS OCTEON3. https://bugs.kde.org/show_bug.cgi?id=344524#c8 (and 9 and 10). This provides a correct implementation, including coverage of ABA cases, for threads within an application, and (IIUC) CAS-level atomicity between a Valgrinded process and a non-Valgrinded process that communicate via shared memory. So it's not perfect, but it might be good enough. Also, it's simple and non-intrusive and so could be done quickly. I would be inclined to preserve the current implementation and use the above only for cores where the current implementation fails, since the current implementation is ABA-correct both for threads within a process and across processes. IOW the proposal is a best-effort fallback. Andrew, is there a way to automatically detect the relevant cores at startup time, so that V can transparently switch to using the fallback implementation without intervention from the user? Peter, do you have any further information about the assertion that "realworld code doesn't really care"? I'd be interested to know more about that. -- You are receiving this mail because: You are watching all bug changes.
