nico wrote: Yes, but we have tests that are sensitive to this, and we already updated them when we rolled in the original libc++ change. Our options are now:
* disable them until both clang and libc++ have rolled, then remember to enable them again (and lose the libc++ optimization we had picked up until then) * put `__has_feature(...)` checks in the test and then remember to remove it again once both have rolled (and also lose the optimization until then) https://github.com/llvm/llvm-project/pull/158523 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
