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.

Sign up for GitHub

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

Jump to bottom

Profile Has Incomplete Allocation Coverage #6

Open
SusanTan opened this issue Jul 10, 2020 · 3 comments
Open

Profile Has Incomplete Allocation Coverage #6

SusanTan opened this issue Jul 10, 2020 · 3 comments
Labels
bug Something isn't working

Comments

@SusanTan
Copy link
Collaborator

SusanTan commented Jul 10, 2020 •
edited
Loading

Benchmark: 505.mcf
How to reproduce: inlining enabled, check benchmark.collaborative-pipeline.dump
image
@SusanTan SusanTan mentioned this issue Jul 10, 2020
Open
@SusanTan SusanTan added the bug Something isn't working label Jul 10, 2020
@SusanTan SusanTan mentioned this issue Jul 10, 2020
Open
@sapostolakis
Copy link
Collaborator

The problem here is that there is an indirect call. The sorting function in SPEC takes the compare function as a function pointer. Inlining would not help since sorting is a recursive function. A possible solution would be to specify the sorting function's memory footprint and never get into the function and stumble upon the cmp call.

@SusanTan
Copy link
Collaborator Author

SusanTan commented Jul 12, 2020 •
edited
Loading

image
Benchmark: 525.x264
How to reproduce: inlining disabled, check benchmark.collaborative-pipeline.dump

@sapostolakis
Copy link
Collaborator

Commit ca93afe resolved a few of these incomplete coverage errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sapostolakis @SusanTan