The constants (cppreference) are useful to avoid false sharing. They're easier to use than relying on platform-specific cacheline-size macros or sysconf or whatnot. Should be safe to use.(The story: after profiling false sharing hits with 'perf c2c' I found some places in Chromium where the constants could be useful).
--
You received this message because you are subscribed to the Google Groups "cxx" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cxx+uns...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/cxx/CAFd1ZwcJkRUt40gn%3DVm-Ud%2B3G1bWvuhw-3hxsRh8Yddg--j8Jw%40mail.gmail.com.
The constants (cppreference) are useful to avoid false sharing. They're easier to use than relying on platform-specific cacheline-size macros or sysconf or whatnot. Should be safe to use.(The story: after profiling false sharing hits with 'perf c2c' I found some places in Chromium where the constants could be useful).
--
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/cxx/CAAHOzFCqmMwV_GiOQ7Em-rDRJ-bofAdby2L4-s0%2BkKECDB0a%3Dw%40mail.gmail.com.
Update: The version of clang in Chromium should now support the macros libc++ uses to implement these features. Accordingly, I think it should be safe to unban-and-convert-to these (though I haven't double-checked yet).