[BISECT] Revert 7ad346c14cd4 (Gigacage→FastMalloc fold) on main#195
Open
sosukesuzuki wants to merge 1 commit intomainfrom
Open
[BISECT] Revert 7ad346c14cd4 (Gigacage→FastMalloc fold) on main#195sosukesuzuki wants to merge 1 commit intomainfrom
sosukesuzuki wants to merge 1 commit intomainfrom
Conversation
This reverts commit 7ad346c.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (26)
💤 Files with no reviewable changes (3)
WalkthroughThis pull request refactors WebKit's memory allocation architecture by extracting Gigacage functionality from FastMalloc into dedicated Gigacage header and implementation files. Approximately 17 files update their includes to reference the new Gigacage module, while FastMalloc removes Gigacage-related declarations. Additional changes update build configurations and adjust symbol visibility in bmalloc's libpas layer. Changes
🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
Preview Builds
|
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.
Reverts
7ad346c14cd4([Build Speed] 2s speedup in clean WTF+bmalloc build) — the only remaining commit in d924138..d550dd3 that touches Wasm memory backing (BufferMemoryHandle.cpp,WasmMemory.cpp,CagedPtr.h, Gigacage→FastMalloc fold, bmalloc heap changes) and was not part of #190's IPInt-asm reverts.Windows-x64 pglite
OutOfBoundsMemoryAccess(oven-sh/bun#29393) reproduces withJSC_useJIT=0(IPInt-only, no tier-up) and does not reproduce withJSC_useWasmIPInt=0(BBQ-only). #190's 8-revert build is byte-identical to pre-upgrade forInPlaceInterpreter*.asm,WasmIPIntSlowPaths.*,WasmIPIntGenerator.*andWasmFunctionIPIntMetadataGenerator.*yet still fails on CI — so the regression is in something IPInt reads, not IPInt code.This commit changes how Wasm linear-memory backing storage is allocated/caged. If folding Gigacage into FastMalloc shifted the Windows path's
boundsCheckingSizeor memory-handle sizing, IPInt's pinned-register bounds check would mis-throw.Not for merge — preview build only. Points the matching Bun PR's
WEBKIT_VERSIONhere once the Windows preview lands.