diff options
| author | Chris Robinson <[email protected]> | 2014-07-31 04:19:33 -0700 |
|---|---|---|
| committer | Chris Robinson <[email protected]> | 2014-07-31 04:19:33 -0700 |
| commit | 6ce464aed89de37c519fad36d17fa9b9ba7819e5 (patch) | |
| tree | 9ce2136ff4d1e2afd00b1792e6a4acc1e7a187c0 /examples | |
| parent | 7c847e62c3825621dc6ce2acc793e821d61ce057 (diff) | |
Avoid a CPU memory fence, and better order memory barriers to accesses
Code produced by GCC 4.9's C11 atomic implementation does not seem to add a
CPU memory fence even with memory_order_seq_cst. Unnecessary memory fences
will be a detriment to performance, so they should only be added if needed.
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions