Skip to content
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

remove spurious gc_try_claim_and_push #75

Merged
merged 1 commit into from
Sep 27, 2023
Merged

remove spurious gc_try_claim_and_push #75

merged 1 commit into from
Sep 27, 2023

Conversation

d-netto
Copy link
Member

@d-netto d-netto commented Sep 25, 2023

PR Description

Shouldn't affect correctness and should have a minimal effect on performance. We already fixed this upstream in JuliaLang#49780.

Checklist

Requirements for merging:

@d-netto d-netto requested a review from kpamnany September 25, 2023 16:07
@kpamnany kpamnany merged commit 9bab9f4 into v1.9.2+RAI Sep 27, 2023
1 check passed
@kpamnany kpamnany deleted the dcn-gc-fix branch September 27, 2023 15:23
@nickrobinson251
Copy link
Member

@d-netto please can you set the port-to-* labels as appropriate? (sorry, this PR was opened before i'd got them up and running)
let me know if you've questions!

@d-netto
Copy link
Member Author

d-netto commented Sep 27, 2023

We merged this before the 1.10 feature freeze. So given that we've already backported to 1.9, then the ports to 1.10 and master might not be necessary? Not sure though.

@kpamnany
Copy link
Collaborator

kpamnany commented Sep 27, 2023

I think we still need the port to 1.9 label because this has to be backported to 1.9.3 when we upgrade to that.

If it's in 1.10 upstream then I think you're right that we don't need that label or the one for master.

@nickrobinson251
Copy link
Member

nice that it's in 1.10!

yeah, exactly as Kiran says, unless it's backported to v1.9 upstream, we need port-to-1.9 label

@d-netto d-netto added the port-to-v1.9 This change should apply to Julia v1.9 builds label Sep 27, 2023
@kpamnany kpamnany removed the port-to-v1.9 This change should apply to Julia v1.9 builds label Oct 19, 2023
github-actions bot pushed a commit that referenced this pull request Dec 16, 2024
Stdlib: SHA
URL: https://github.com/JuliaCrypto/SHA.jl.git
Stdlib branch: master
Julia branch: master
Old commit: aaf2df6
New commit: 8fa221d
Julia version: 1.12.0-DEV
SHA version: 0.7.0(Does not match)
Bump invoked by: @inkydragon
Powered by:
[BumpStdlibs.jl](https://github.com/JuliaLang/BumpStdlibs.jl)

Diff:
JuliaCrypto/SHA.jl@aaf2df6...8fa221d

```
$ git log --oneline aaf2df6..8fa221d
8fa221d ci: update doctest config (#120)
346b359 ci: Update ci config (#115)
aba9014 Fix type mismatch for `shake/digest!` and setup x86 ci (#117)
0b76d04 Merge pull request #114 from JuliaCrypto/dependabot/github_actions/codecov/codecov-action-5
5094d9d Update .github/workflows/CI.yml
45596b1 Bump codecov/codecov-action from 4 to 5
230ab51 test: remove outdate tests (#113)
7f25aa8 rm: Duplicated const alias (#111)
aa72f73 [SHA3] Fix padding special-case (#108)
3a01401 Delete Manifest.toml (#109)
da351bb Remvoe all getproperty funcs (#99)
4eee84f Bump codecov/codecov-action from 3 to 4 (#104)
15f7dbc Bump codecov/codecov-action from 1 to 3 (#102)
860e6b9 Bump actions/checkout from 2 to 4 (#103)
8e5f0ea Add dependabot to auto update github actions (#100)
4ab324c Merge pull request #98 from fork4jl/sha512-t
a658829 SHA-512: add ref to NIST standard
11a4c73 Apply suggestions from code review
969f867 Merge pull request #97 from fingolfin/mh/Vector
b1401fb SHA-512: add NIST test
4d7091b SHA-512: add to docs
09fef9a SHA-512: test SHA-512/224, SHA-512/256
7201b74 SHA-512: impl SHA-512/224, SHA-512/256
4ab85ad Array -> Vector
8ef91b6 fixed bug in padding for shake, addes testcases for full code coverage (#95)
88e1c83 Remove non-existent property (#75)
068f85d shake128,shake256: fixed typo in export declarations (#93)
176baaa SHA3 xof shake128 and shake256  (#92)
e1af7dd Hardcode doc edit backlink
```

Co-authored-by: Dilum Aluthge <[email protected]>
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.

3 participants