update pinned build to clang 18.1.8 #400
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the pinned build to clang 18.1.8. Normally I wouldn't have advocated for moving from 17->18 but I stumbled on a c++20 feature that while it's in libstdc++10, is still missing from libc++17 but just added to libc++18:
jthread
. There seems to be an appetite to take on environment upgrades (e.g. #336) so nice to fill out c++20 support more before 1.0 release.I measured something around a 0.5% speed improvement for a replay over blocks 381452700 through 381632370 (sadly I didn't think to include #344 as part of that; though at least we know #344 wouldn't have been resolved just by updating to clang18).
The upgrade may also unlock another useful feature:
_LIBCPP_HARDENING_MODE
was added in 18 and is similar to_GLIBCXX_ASSERTIONS
in enabling stdlib hardening checks intended to be operational in production. To be explored still.This PR also tweaks the Dockerfile to remove intermediary build files at each step instead of at the end. This reduces the size of Docker's build cache from ~20GB to ~14GB