perf(coro): fuse synchronous child await transactions - #164
Merged
Conversation
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.
Summary
llvm.coro.resume/done/destroyin generated callers while fusing allocation-elided destroy, parent reactivation, and completion consumptionValidation
-racetime.SleepE2E tests pass_testmetafixtures pass in isolated processesgo build -p=1 ./cmd/llgopassesThe aggregate metadata command was intentionally stopped when one long-lived LLVM process reached about 3.5 GiB RSS; the same 12 fixtures all passed when process-isolated. No process remained afterward.
Measured checkpoint
Darwin arm64, Go 1.26.5, LLVM 22.1.8, full LTO, same
io_workloadsource and independent caches:__text: 4,152,648 -> 4,073,188 bytes (-1.91%)Wall-clock file timing was noisy on the shared host, so no stable wall-time percentage is claimed.
Known independent gap
The
_testgo/goexitfixture still stops before LIT checking on the pre-existingunsupported outcome-plain terminal outcome recipe goexitgap. This PR updates its ABI expectation but does not expand outcome-plain semantics.