Skip to content

Accept either don't-resolve-refs flag in the i386 gate search - #16

Closed
natbro wants to merge 1 commit into
NotProtonNot:devfrom
natbro:i386-gate-flags
Closed

natbro wants to merge 1 commit into
NotProtonNot:devfrom
natbro:i386-gate-flags

Conversation

@natbro

@natbro natbro commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

wine renamed the constant between 11.0 and 11.15 and its value changed with it: DONT_RESOLVE_DLL_REFERENCES is 0x1, LDR_DONT_RESOLVE_REFS is 0x2. build_module carries the same source line either way, so the gate search has to accept both.

Without this, resolve.py reports "no module-flags gate above the MODREF flag test" for anything built from wine 11.0, CrossOver 26.3 among them. With it, 26.3's i386 ntdll resolves and steals the gate plus its jne, the same shape the pinned Rosetta i386 build already uses.

wine renamed the constant between 11.0 and 11.15 and its value changed with it:
DONT_RESOLVE_DLL_REFERENCES is 0x1, LDR_DONT_RESOLVE_REFS is 0x2. build_module
carries the same source line either way, so the gate search has to accept both.

Without this, resolve.py reports "no module-flags gate above the MODREF flag
test" for anything built from wine 11.0, CrossOver 26.3 among them. With it,
26.3's i386 ntdll resolves and steals the gate plus its jne, the same shape the
pinned Rosetta i386 build already uses.
@natbro

natbro commented Oct 2, 2026

Copy link
Copy Markdown
Contributor Author

dupe of broader resolution in dev branch, a9c6dc3

@natbro natbro closed this Oct 2, 2026
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.

1 participant