Skip to content

Conversation

Michael137
Copy link
Member

This patch moves the frame_lang logic to just the logging (because that's what it was always used for anyway). The callsites decide whether to fall back on to the frame language or not when running the expression.

This patch moves the `frame_lang` logic to just the logging (because
that's what it was always used for anyway). The callsites decide whether
to fall back on to the frame language or not when running the
expression.
@Michael137 Michael137 force-pushed the lldb/frame-lang-cleanup branch from 72e80ed to 7ff4946 Compare September 3, 2025 10:35
@Michael137 Michael137 requested a review from labath September 3, 2025 11:38
Copy link
Contributor

@felipepiovezan felipepiovezan left a comment

Choose a reason for hiding this comment

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

I think this is fine, but that FIXME is curious. We don't support running in non-C++ modes, so switching on frame_lang would only get us a more precise C++ standard version, but do we use that?

@Michael137
Copy link
Member Author

I think this is fine, but that FIXME is curious. We don't support running in non-C++ modes, so switching on frame_lang would only get us a more precise C++ standard version, but do we use that?

Yea it was me who added the FIXME back when I was refactoring some of this code a while back. We do use the "more accurate language standards", but we set the frame language at the callsite anyway. So decided to remove this FIXME

@Michael137 Michael137 merged commit 25a3045 into llvm:main Sep 3, 2025
9 checks passed
@Michael137 Michael137 deleted the lldb/frame-lang-cleanup branch September 3, 2025 14:52
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