ci: bump actions/cache/restore from 4.3.0 to 6.1.0 - #5
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [actions/cache/restore](https://github.com/actions/cache) from 4.3.0 to 6.1.0. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@0057852...55cc834) --- updated-dependencies: - dependency-name: actions/cache/restore dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Ttimmahlax
pushed a commit
that referenced
this pull request
Aug 20, 2026
…62 -> 132.00 (-20.62 Ir/op) The public zalloc/calloc did malloc(size) then zero_block(p, is_zero), and zero_block's non-zero arm (taken on every RECYCLED block, i.e. the steady calloc churn path) called usable_size(p): mask to the segment, resolve the page, check the segment kind, un-align — all to recover a block_size the allocator held one field-load away. New Heap::zalloc pops the block with the page still in hand and zeroes using (*p).block_size directly. The re-resolution is gone from the hot recycled path; the rare slow/large path still recovers it the general way. Measured (callgrind opscan, freshly built): calloc 152.62 -> 132.00, 0.949x -> 0.820x vs mimalloc. Every other op is BYTE-IDENTICAL — small 79.38, batch_lifo 60.17, realloc 379.53, mixed 140.07 — because the plain malloc/free path is not touched; only the zeroing entry point changed. The stronger-than-mimalloc full-extent zeroing contract is preserved: zalloc still zeroes the whole usable extent, and zalloc_is_zero_across_the_whole_usable_extent still passes. Verified: workspace release green, all-features clippy clean, secure+blockmap suite green (bar the documented WSL purge flake). Also in this commit, opps.md #3 (bounds-check audit): 39 panic_bounds_check sites lib-wide, but ZERO reachable from the shipped malloc / free / calloc fast paths (confirmed by disassembling the override .so). All 39 are on slow/cold paths. The safe-Rust hot path pays no bounds-check tax. Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>
Ttimmahlax
pushed a commit
that referenced
this pull request
Aug 20, 2026
…code #3 bounds-check audit — DONE, and the headline is that there is nothing to fix on the hot path: 39 panic_bounds_check sites lib-wide, ZERO reachable from the shipped malloc / free / calloc fast paths (confirmed on the override .so). All 39 are on slow/cold paths (segment alloc/free, visitors, arena, teardown, and 2 on the malloc_generic refill). The safe-Rust allocator pays no bounds-check tax where it matters. The 2 refill checks resisted a min(MAX_NORMAL_BIN) clamp on bin (count unchanged) and sit on a cold path — not worth chasing, recorded so the dead end is not re-explored. #4 update_direct recompute — ASSESSED, premise false. bin_size(bin) for the common bin <= 8 is bin << 3 (a shift), and bin_size(bin-1) runs only for bin > 8. There is no costly recompute on the hot path, and replacing the shift with a table/stored load would reintroduce a panic_bounds_check (bin from bins::bin is unbounded to LLVM) that costs more than it saves. Left as-is. Both are honest negative results with the evidence attached, which is the point of the register: they stop the next person re-attempting a dead end. The Tier-2 win that DID land is #5 (calloc -20.62 Ir/op), committed separately. Co-Authored-By: Claude Fable 5 (1M context) <noreply@anthropic.com>
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.
Bumps actions/cache/restore from 4.3.0 to 6.1.0.
Release notes
Sourced from actions/cache/restore's releases.
... (truncated)
Changelog
Sourced from actions/cache/restore's changelog.
... (truncated)
Commits
55cc834Merge pull request #1768 from jasongin/readonly-cached8cd72fBump@actions/cacheto v6.1.0 - handle cache write error due to RO token2c8a9bdMerge pull request #1760 from actions/samirat/esm_migration_and_package_updatee9b91fdPrettier fixese4884b8Rebuild dist10baf01Fixed licensese39b386Fix test mock return orderb692820PR feedback6074912Rebuild dist bundles as ESM to match type:module5a912e8Fix lint and jest issuesDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)