You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using uppercase register names causes some instructions to not match properly, ultimately leading to a loss of throughput/latency information in the analysis output
Expected behavior
It should function as below regardless of case. Since it only happens with some instructions the problem is probably while building the data cache for the HW model. But maybe a simple force to lowercase in the parser would make sense too.
Describe the bug
Using uppercase register names causes some instructions to not match properly, ultimately leading to a loss of throughput/latency information in the analysis output
To Reproduce
Steps to reproduce the behavior:
osaca --arch V2 lbc.gh.nvfortran_upper.s
OSACA output
This is the output with uppercase registers with many missing latency matches.
Expected behavior
It should function as below regardless of case. Since it only happens with some instructions the problem is probably while building the data cache for the HW model. But maybe a simple force to lowercase in the parser would make sense too.
Additional context
This assembly snippet is from code compiled with the nvfortran compiler on a Grace Hopper machine
The text was updated successfully, but these errors were encountered: