I would also check if the problem disappears if you compile with: `-O0`. If it does disappear, then I would just do `asm volatile("": : :"memory")` instead of the full memory barrier. This has no runtime effect, it just makes GCC more careful with instruction reordering when doing optimizations.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/404#issuecomment-240899716
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
