Pull latest libakerror: static TLS fix landed
All checks were successful
akbasic CI Build / cmake_build (push) Successful in 3m25s
akbasic CI Build / sanitizers (push) Successful in 4m48s
akbasic CI Build / coverage (push) Successful in 4m18s
akbasic CI Build / akgl_build (push) Successful in 8m6s
akbasic CI Build / mutation_test (push) Successful in 16m49s
All checks were successful
akbasic CI Build / cmake_build (push) Successful in 3m25s
akbasic CI Build / sanitizers (push) Successful in 4m48s
akbasic CI Build / coverage (push) Successful in 4m18s
akbasic CI Build / akgl_build (push) Successful in 8m6s
akbasic CI Build / mutation_test (push) Successful in 16m49s
libakerror main now includes the fix for issue #37 (per-TU static TLS akerr_last_ignored -> single extern definition in src/error.c, one copy per thread instead of one per translation unit) and issue #38 (project() now stamps 2.0.3, matching the release notes). Bump deps/libakerror to origin/main (9249f8c) and update MAINTENANCE.md: drop the now-stale 'IGNORE change costs' subsection and the 2.0.2/2.0.3 version-disagreement note, since both are resolved upstream. Verified: build/basic has no TLS segment and zero -Wunused-variable warnings for akerr_last_ignored; 114/114 tests pass. Co-Authored-By: Andrew Kesterson <andrew@aklabs.net>
This commit is contained in:
2
deps/libakerror
vendored
2
deps/libakerror
vendored
Submodule deps/libakerror updated: ee38eed31c...9249f8c029
Reference in New Issue
Block a user