http://bugzilla.opensuse.org/show_bug.cgi?id=1133245 http://bugzilla.opensuse.org/show_bug.cgi?id=1133245#c20 --- Comment #20 from Dr. Werner Fink <werner@suse.com> --- (In reply to Martin Liška from comment #18)
In fact in past I had used memory barriers in the body of for loops where the code was only in the boolean and incremental statement to avoid that those loops become removed.
Well you should probably use volatile for the variables which can be influenced by a handlers. Doing that the memory barious should not be needed.
In fact using `volatile sig_atomic_t' does also work. Interesting question why the type sig_atomic_t is not defined with attribute volatile in <bits/types.h> -- You are receiving this mail because: You are on the CC list for the bug.