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

A few follow ups to #8978 and user stack maps and safepoints #8991

Merged

Conversation

fitzgen
Copy link
Member

@fitzgen fitzgen commented Jul 22, 2024

See each commit for details.

This is purely mechanical code motion.
These are all inside a "safepoint" module, and `env_logger` prints the module
before the log message, so the old "stack map" part of the log messages' prefix
is a bit redundant now.
These comments were referencing things that we did in the old implementation of
stack maps and safepoints, and have been updated for the new approach.
@fitzgen fitzgen requested a review from a team as a code owner July 22, 2024 18:32
@fitzgen fitzgen requested review from cfallin and removed request for a team July 22, 2024 18:32
@github-actions github-actions bot added the cranelift Issues related to the Cranelift code generator label Jul 22, 2024
Copy link
Member

@elliottt elliottt left a comment

Choose a reason for hiding this comment

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

Looks great!

@fitzgen fitzgen added this pull request to the merge queue Jul 22, 2024
Merged via the queue into bytecodealliance:main with commit 80c42c4 Jul 22, 2024
37 checks passed
@fitzgen fitzgen deleted the user-stack-maps-and-moving-gc-follow-up branch July 22, 2024 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cranelift Issues related to the Cranelift code generator
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants