-
Notifications
You must be signed in to change notification settings - Fork 49
cl, ssa: fold composite literal stores, support struct slice static inits, and add LTO baseline benchmarks #2375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
cpunion
wants to merge
4
commits into
xgo-dev:main
from
cpunion:codex/static-init-struct-slice-on-main
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
b13567e
cl, ssa: fix zero-sized global init and fold composite literal alloc …
cpunion 448dae3
benchmark: use PR merge-base for baseline and add LTO workload measur…
cpunion 8b5d5cb
cl: support static initializer folding for struct and composite slices
cpunion d565df7
cl: support recursive address projections in collectAllocStores
cpunion File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P3] Untrusted event fields interpolated into a run step
The
Determine pull request merge-basestep expands${{ github.event.pull_request.* }}directly into a shellrun:block — the canonical GitHub Actions script-injection shape. Severity is low here: the trigger ispull_request(read-onlyGITHUB_TOKEN, no secrets),head.shais a hex SHA, andbase.repo.full_name/base.refare base-side (maintainer-controlled for fork PRs). Recommend passing these throughenv:and referencing quoted shell variables (e.g."$BASE_REF","$HEAD_SHA") so the workflow stays safe against future refactors (e.g. topull_request_target).