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

Fix and improve debug counters for failed call sites #7410

Merged
merged 2 commits into from
Jul 30, 2024

Conversation

jdmpapin
Copy link
Contributor

  • Create debug counters correctly for removed call sites
  • Specify the current compilation in failed call site debug counter names

This was passing callsite->_callNodeTreeTop while it was still null,
which prevented the debug counter increment from being generated and
even prevented a static debug counter increment.

The treetop where the call occurs is tt, and in this case callsite is
the result of searching for a dead call site that matches it. This tt
is already used for the Unresolved_In_ECS case, and it's also the value
that callsite->_callNodeTreeTop would take on just below if callsite
hadn't been removed.
This way, if a particular failure reason is of interest, the debug
counters will list all of the methods in which inlining failed for that
reason.
@0xdaryl 0xdaryl self-assigned this Jul 30, 2024
@0xdaryl
Copy link
Contributor

0xdaryl commented Jul 30, 2024

Jenkins build all

@0xdaryl 0xdaryl merged commit a0f9acd into eclipse-omr:master Jul 30, 2024
16 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants