Skip to content

Backport "-Yprofile-trace properly report macro splicing source" to 3.3 LTS #492

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

Merged
merged 2 commits into from
Jul 9, 2025

Conversation

tgodzik
Copy link

@tgodzik tgodzik commented Jul 8, 2025

Backports scala#23488 to the 3.3.7.

PR submitted by the release tooling.

smarter and others added 2 commits July 8, 2025 15:07
Previously when we had some code like:

def userCode: Unit =
  ...
  val x = myExpensiveMacro()
  ...

The profiler reported the time spent executing the macro as `«method userCode»`
which is misleading. This commit changes it to be reported as `«method
myExpensiveMacro»`. This is particularly useful in bottom-up profiling to find
which macros we spend the most amount of time in.

[Cherry-picked 7f81cc5]
Base automatically changed from backport-lts-3.3-23484 to lts-3.3 July 9, 2025 16:00
@tgodzik
Copy link
Author

tgodzik commented Jul 9, 2025

No regressions detected in the community build up to backport-lts-3.3-23488.

Reference

@tgodzik tgodzik merged commit d743501 into lts-3.3 Jul 9, 2025
22 checks passed
@tgodzik tgodzik deleted the backport-lts-3.3-23488 branch July 9, 2025 16:00
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