Repository navigation
CI ratchets after the 0.12.0 upstream merge (clang-tidy, host warnings) - #36
Merged
Merged
Conversation
…two nil archives guarded in t_pso_stall, baseline 237 -> 220 - nvn_mtl.m: NOLINT with the reason on eight analyzer findings in landed code: a shift by __builtin_ctz of a nonzero word, indices bounded by the line before (addressed ranges, vertex streams, g_mrb, g_mrbuf), and two objects held by hm_put_id maps - t_depth16_clear, t_dlss_mfx, t_ndve_movie, t_pool_heap, t_upscaler_mfx: g_tex_live keeps the address a texture was initialized at; mtl_tex_release reads it through vm_read_overwrite and checks magic and serial, so a helper returning its tex_t by value is safe (NOLINT StackAddressEscape) - t_feedback: the bf_key offsets are int8_t on purpose (-1 = none) - t_pso_stall: an archive that does not open is left out instead of added as nil - lint_c_baseline.tsv: tidy --update (11 file/check pairs had fewer findings; t_view_swizzle back below main's) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016qteK29T18U8p1c9LsVY8g
…t (host warnings ratchet) mtl_tex_init passed its const tex_t * to nvn_hm_put's void * value, a new -Wincompatible-pointer-types-discards-qualifiers warning from the 0.12.0 upstream merge (upstream stores (void *)1 there). The map only reads the address back (mtl_tex_release, as a const tex_t *), so the cast is safe. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016qteK29T18U8p1c9LsVY8g
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What and why
Two CI ratchets went red on the 0.12.0 release PR (#35) after the upstream merge: clang-tidy (lint-c) and the Mac host compiler-warnings check in Build check. The release shipped without these fixes, so main is red on both until this PR lands.
f983a79: clang-tidy. The LLVM 23.1.4 analyzer flags code that landed with the upstream merge.
dm/gfx/nvn/nvn_mtl.m: a NOLINT, with the reason on the same line, on eight analyzer false positives:__builtin_ctzof a nonzero word.g_mrb,g_mrbuf).hm_put_idmaps.t_depth16_clear,t_dlss_mfx,t_ndve_movie,t_pool_heap,t_upscaler_mfx: a NOLINT for StackAddressEscape ong_tex_live.mtl_tex_releasereads the stored address throughvm_read_overwriteand checks magic and serial, so a helper that returns itstex_tby value is safe.t_feedback: a NOLINT for bugprone-signed-char-misuse. Thebf_keyoffsets areint8_ton purpose (-1 = none).t_pso_stall: a real fix. An archive that doesn't open is now left out instead of being added as nil.dm/tools/lint_c_baseline.tsv: regenerated withtidy --update. 11 file/check pairs now have fewer findings, andt_view_swizzleis back below main's count.d27661c: host warnings.
mtl_tex_initpassed itsconst tex_t *tonvn_hm_put'svoid *value, which is a new-Wincompatible-pointer-types-discards-qualifierswarning (upstream stores(void *)1at that point). The map only reads the address back, inmtl_tex_releaseas aconst tex_t *, so an explicit cast is safe.Checked
--against origin/main, rc 0, 220 findings against a baseline of 220 (down from 237), and 0 pairs above the baseline.t_feedbackfailed 1 of 193 on an earlier run where only a comment had changed, so it looks flaky. That failure isn't related to this change.Docs
🤖 Generated with Claude Code
https://claude.ai/code/session_016qteK29T18U8p1c9LsVY8g