Skip to content

Propagate Debugging Identifiers through the Middle End #3967

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

Draft
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

spiessimon
Copy link
Contributor

This PR builds on top of #3942. It propagates the debugging identifiers from Lambda through Flambda.

@spiessimon spiessimon added flambda2 Prerequisite for, or part of, flambda2 middle end lambda Lambda language changes labels May 5, 2025
Comment on lines 1197 to 1199
(* CR sspies: We can probably find a better
[Flambda_debug_uid.t] for these extra variables. However,
propagating it here seems non-trivial. *)
Copy link
Contributor

Choose a reason for hiding this comment

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

FYI variables with Name_mode.in_types never exist at runtime (roughly speaking, they are used when we have information on something that doesn't have a name in the current scope), it's probably not useful for them to have a debug uid.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah, that's very useful to know! I've updated the comment here and in a few other places to indicate that Flambda_debug_uid.none is correct here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dwarf and debugging flambda2 Prerequisite for, or part of, flambda2 lambda Lambda language changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants