Also, fix the last issue that prevented GCC 11 from passing the test
suite. Thanks to everyone else who fixed issues.
Details
- Reviewers
- None
- Group Reviewers
Restricted Project Restricted Project - Commits
- rG4f194d0db78f: [libc++] Promote GCC 11 to mandatory CI
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
libcxx/test/std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_is_lock_free.pass.cpp | ||
---|---|---|
30–32 | Whatever change is made to t probably also needs to be made to vt. | |
libcxx/utils/ci/Dockerfile | ||
61 | I'd leave this comment as "a recent GCC", since otherwise it'll be lying in a few months from now. | |
libcxx/utils/ci/buildkite-pipeline.yml | ||
138–149 | Would it be an unconscionable waste of buildkite resources to just leave this here, and update the gcc-next target to GCC 12 when it's released? As with the comment above, it seems silly to be churning this stuff around twice per GCC-release-cycle, when we could get away with updating it just once per GCC-release-cycle. |
Address review comments and clarify intent about supported versions.
libcxx/utils/ci/Dockerfile | ||
---|---|---|
61 | Actually, I think it's important to document the intent here. See my next update, hopefully it makes it clearer what we're trying to do. |
libcxx/utils/ci/Dockerfile | ||
---|---|---|
61 | OK, I buy this new phrasing. LGTM. |
libcxx/test/std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_is_lock_free.pass.cpp | ||
---|---|---|
30 | This initialization and the similar one below would not work from C++14 and below. |
This initialization and the similar one below would not work from C++14 and below.
std::atomic is not copy construtible, and only starting from C++17 this initialization here from a prvalue of the same type performs direct initialization, and not a copy.