Skip to content

Fix Windows CI: alloc_watch MSVC caller-site intrinsic - #51

Merged
offdev merged 1 commit into
masterfrom
fix/windows-ci-alloc-watch-msvc-intrinsic
Sep 24, 2026
Merged

offdev merged 1 commit into
masterfrom
fix/windows-ci-alloc-watch-msvc-intrinsic

Conversation

@offdev

@offdev offdev commented Sep 24, 2026 •

Copy link
Copy Markdown
Owner

CI confirmed: the reopened-triggered run 36034935261 ran the windows-msvc job — build clean (no C2065, no warnings), ctest 92/92 passed (74.9 s), all platform-independent jobs green.

The M1-ALLOC-01 allocation watch captures the first offending
allocation's call site via LAIGE_ALLOC_CALLER_SITE(). The MSVC branch
spelled the intrinsic GCC-style (__return_address), which does not
exist on MSVC — C2065 (undeclared identifier) in all four operator
new overrides, failing the windows-msvc Build step on master (run
36030996286, job 107739418055).

Use the MSVC _ReturnAddress() intrinsic from <intrin.h> (same
caller-frame semantics as __builtin_return_address(0): the address of
the allocating call), and update the two doc mentions that repeated
the wrong name (docs/api/alloc_watch.md, roadmap/README.md).

Verified: the change is inside the _MSC_VER branch only; a fresh
canonical Debug g++ build of laige-core compiles warning-free.
@offdev offdev closed this Sep 24, 2026
@offdev offdev reopened this Sep 24, 2026
@offdev
offdev merged commit e68ecd0 into master Sep 24, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant