Skip to content

fix(driver): restore numeric diagnostic format specifiers - #8

Open
pogorskii wants to merge 1 commit into
knewnothing-git:mainfrom
pogorskii:fix/diagnostic-format-strings
Open

fix(driver): restore numeric diagnostic format specifiers#8
pogorskii wants to merge 1 commit into
knewnothing-git:mainfrom
pogorskii:fix/diagnostic-format-strings

Conversation

@pogorskii

Copy link
Copy Markdown

Debug messages currently print literal type names instead of RAM amounts and inference counters. In allocation/free logs, the missing conversion also shifts the byte count into the following pointer conversion. This restores the seven numeric format strings and casts the GPU address to the unsigned type expected by %llX.

Fixes #7.

Validation against the repository's non-Windows stubs, using GCC 13.3.0 on Linux x86-64:

  • The original revision fails strict compilation with format errors; all eight driver C source files pass after the change using the warning flags in CMakeLists.txt.
  • A runtime harness invokes device add/remove and a 64-byte allocation/free lifecycle. It checks the actual RAM, pointer and GPU-address output, counters above 32 bits, and balanced allocation accounting.
  • git diff --check passes.

Windows/WDK compilation and hardware inference were not tested. The documented scripts/test.ps1 is absent from this revision. Prepared with AI assistance; the compiler and runtime checks were executed locally.

The associated issue requests eligibility confirmation for the published ₹250 reproducible-bug bounty. If accepted, please indicate a private channel to arrange the documented international Wise payout. No payment details are included publicly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Diagnostic format strings fail Linux syntax checks and omit numeric values

1 participant