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.

Sign up for GitHub

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

Jump to bottom

[release-1.9] Backport #48751 and #48832 #48881

Merged
merged 2 commits into from
Mar 6, 2023
Merged

[release-1.9] Backport #48751 and #48832 #48881

merged 2 commits into from
Mar 6, 2023

Conversation

vchuravy
Copy link
Member

@vchuravy vchuravy commented Mar 3, 2023

@vchuravy
Copy link
Member Author

vchuravy commented Mar 3, 2023

Need to fix authorship on one of the commits

@vtjnash @vchuravy
staticdata: make hookup of code instances correct (#48751)
65a025f 
Previously we would double-account for many of these, leading to
occasional chaos. Try to avoid serializing code that does not belong to
this incremental compilation session package.

Refs: #48723
(cherry picked from commit 81f366d)
@vtjnash @vchuravy
staticdata: make completeinfo memory-/gc-safe (#48832)
c1cb058 
There is actually almost no cases where `jl_alloc_svec_uninit` is safe,
since if was safe, you would likely would prefer to use the `jl_svec`
constructor instead.

(cherry picked from commit 0608824)
@KristofferC KristofferC merged commit be9df3f into backports-release-1.9 Mar 6, 2023
@KristofferC KristofferC deleted the vc/backports-1.9 branch March 6, 2023 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@vtjnash vtjnash vtjnash approved these changes

@KristofferC KristofferC Awaiting requested review from KristofferC

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@vchuravy @vtjnash @KristofferC