Install: Build v3.0.0-rc.4 fails compiling code_051.c with malformed _src/$_dst declaration #985
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#985
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reported by BobbyTortilla on Discord
What you used
Longshot Launcher v1.0.0-rc.9 (portable), building with the Longshot builder.
Version and channel
Build v3.0.0-rc.4 (release candidate). The same failure happened on launcher rc.7 and rc.9. It also reproduces with Longshot nightly-287-0407ae24.
Where it stopped
Build stopped during Compile at 53% (
make_game.py/build.py, exit status 1), while compilingcode_051.con the rc.4 attempt. On nightly-287 it stopped compilingcode_026.cafter 728 seconds total; that file took 7 seconds compiling alone.Error
On rc.4:
The compiler output also shows:
There are 3 errors total.
On nightly-287:
One error was reported. The nightly report's final 200 build-log lines and final 29 launcher-log lines are attached to the Discord report.
System and settings
Windows 10.0.26200 x64; .NET 10.0.15; 32 GB RAM, 24 threads. NVIDIA RTX 5070, Game Ready Driver 621.01. Free disk space: 575 GB. Build settings: memory and workers automatic, DLSS on, FSR 4 and XeSS off.
Logs
Launcher bug-report output includes build and launcher log excerpts. Still unknown: exact steps preceding the build attempts and whether other conditions affect reproduction.
Files from the Discord report:
Updated with more from BobbyTortilla on Discord: Added the reporter's RTX 5070, Game Ready Driver 621.01, and 575 GB free disk space; the linked merged launcher PRs do not address this generated-C compiler failure.
From BobbyTortilla on Discord:
BobbyTortilla reports the same compile failure on nightly: it stopped again at 53%, but this attempt reported undeclared identifier
Wminstead. Exact nightly version and full compiler output for this second attempt were not provided. The builder-stop behavior fix in PR #540 is in nightly-285-a8a30c22, but it does not address the underlying generated-C compile error.Updated with more from BobbyTortilla on Discord: Added the exact nightly-287 version and its full Wm undeclared-identifier compiler error/log details.
Files:
Both errors look like one flipped bit in the generated C, not a lift bug. The same bit both times:
code_051.split.c:uint32_t _src[4]$_dst[4]should be_src[4],_dst[4]. ',' is 0x2C and '$' is 0x24.code_026.split.c:memcpy(Wm,c->vreg[1],16)should bememcpy(_m,...). '_' is 0x5F and 'W' is 0x57. The same line spells_mcorrectly a few characters earlier (uint32_t _n[4],_m[4],...).Each is a single byte with bit 3 (0x08) flipped, in a different file on a different build. The translator writes these lines the same way every time, and the same rc.4 and nightly sources build here and for other players. Random single-bit flips like that usually mean memory or CPU instability: an XMP/EXPO memory profile or an overclock that's slightly unstable, or a failing RAM stick. A long build that loads all 24 threads and lots of memory is often the first thing to show it.
Worth trying, in order:
Deleting
work\sa\build\objbefore retrying makes sure no corrupted object is reused.Posted by an AI agent (Claude Code) for d4nkn3ss.