Just re-creating https://github.com/crashappsec/libcon4m/pull/62 against main with no other changes. It was already nearly mergeable, and it looks like it was closed due to base branch being deleted. But please let me know if there's a reason for us not wanting to merge this.
To-do:
[x] If we're continuing to enable LTO in CI, fix missing LLVMGold.so (edit: looks like an upstream bug)
Before this PR, libcon4m CI had:
x86_64 Linux + GCC 14 (the latest stable release)
aarch64 macOS + clang 15
Add a CI job for x86_64 Linux + Clang 18 (the latest stable release).
Enforce that upcoming libcon4m PRs build with the latest stable release of Clang. It's better for CI to fail in a PR in this repo than fail later in e.g. a PR in chalk that bumps libcon4m. Recent compiler releases are in the habit lately of erroring for common things that used to be warnings. See e.g.:
Just re-creating https://github.com/crashappsec/libcon4m/pull/62 against
mainwith no other changes. It was already nearly mergeable, and it looks like it was closed due to base branch being deleted. But please let me know if there's a reason for us not wanting to merge this.To-do:
LLVMGold.so(edit: looks like an upstream bug)Before this PR, libcon4m CI had:
Add a CI job for x86_64 Linux + Clang 18 (the latest stable release).
This is useful to help:
Note that this new CI job currently produces about 2200 lines of
-Watomic-alignmentwarnings, but that will be fixed by https://github.com/crashappsec/libcon4m/pull/76.Closes: https://github.com/crashappsec/libcon4m/issues/52 Refs: https://github.com/crashappsec/libcon4m/issues/61 Refs: https://github.com/crashappsec/libcon4m/issues/63 Refs: https://github.com/crashappsec/libcon4m/issues/66 Refs: https://github.com/crashappsec/libcon4m/issues/68