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

jitdump fixes from upstream #261

Merged
merged 1 commit into from
Mar 26, 2024
Merged

jitdump fixes from upstream #261

merged 1 commit into from
Mar 26, 2024

Conversation

vvuk
Copy link

@vvuk vvuk commented Mar 25, 2024

While upstreaming the jitdump-on-mac work in dotnet#99986 a few correctness issues were discovered. This adds those changes into our branch. There may be some additional tweaks upstream but they will be largely ifdef etc. related.

Copy link

@alexey-zakharov alexey-zakharov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good and matches the upstream PR
question - should we wait for upstream merge in case there are further fixes required?

@vvuk
Copy link
Author

vvuk commented Mar 26, 2024

question - should we wait for upstream merge in case there are further fixes required?

I'm 99% certain that these are the only remaining functional correctness fixes. Anything else from upstream is just going to be ifdef/cmake shenanigans. I'm going to go ahead and merge this here so that we can get an updated build in

@vvuk vvuk merged commit 92cf035 into unity-main Mar 26, 2024
2 checks passed
@vvuk vvuk deleted the real-jitdump branch March 26, 2024 17:55
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.

2 participants