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

Disassembly view: Are assembly lines expected to have near zero cycles? #429

Closed
GitMensch opened this issue Nov 28, 2022 · 5 comments
Closed
Labels

Comments

@GitMensch
Copy link
Contributor

This issue is mostly a question.
Running on Debian with kernel 5.15 and perf 5.15 on this machine.

In an example recording done with perf record --call-graph dwarf,8192 -z --sample-cpu ./dice I see only two lines in Disassembly with a cost attached, but the Source view shows much more (and strangely shows an unreasonable high inclusive cost on a return line):

example disassembly

Are those costs "expected"?

@milianw milianw added the needs_info not enough info label Nov 28, 2022
@milianw
Copy link
Member

milianw commented Nov 28, 2022

please attach the source code to reproduce this, as-is it's unclear whether there should be more or not. do you just have to scroll on the RHS maybe? could also be due to inlining, i.e. most of the cost is in other places potentially?

@GitMensch
Copy link
Contributor Author

Will do, but that will take some time.

@milianw
Copy link
Member

milianw commented Sep 2, 2024

I believe this is a duplicate of #671 but since we don't have any way to reproduce the issue here I'll close this for now. If you think this is not a duplicate, please reopen

@GitMensch
Copy link
Contributor Author

only a GitHub UI+API issue:
duplicate

:-)

In any case I try to reproduce the original case and retest with the current appimage of #672

@milianw milianw closed this as not planned Won't fix, can't repro, duplicate, stale Sep 2, 2024
@GitMensch
Copy link
Contributor Author

Rechecked - I can't reproduce this specific issue with current continous - so closing as "not reproducible" is the right thing to do (and that issue is unrelated to #671)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants