[libcxx-commits] [libcxx] [libc++][Android] Always redirect <stdatomic.h> to <atomic> (PR #143036)

via libcxx-commits libcxx-commits at lists.llvm.org
Thu Jun 12 09:55:48 PDT 2025


enh-google wrote:

> Have you folks looked into removing that historical extension on the Android side? If that's something Android would be open to, I could suggest the following:

our problem is (as you guessed) that this is exposed to app developers and partners (both SoC vendors and device manufacturers). we've tried things like you suggest in the past, and the trouble is that people fall into one of two groups: the -Werror group (who you've now broken) and the "ain't nobody got time for _warnings_" group (who won't do anything until/unless you break them).

given that there's no _advantage_ to breaking anyone, it's hard to justify this.

(don't get me started on the transitive include "cleanup" in c++23 ... that's going to have everyone mad at me :-( )

for <atomic>/<stdatomic.h> is there a way we can move the hackery out into our header which does an `#include_next`?

> Gives plenty of time for Android users to migrate / fix their code (between 1 year and 1.5 years)

(ah, the joys of working for apple :-) )

https://github.com/llvm/llvm-project/pull/143036


More information about the libcxx-commits mailing list