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
Consult the security policy. If reporting a security vulnerability, do not report the bug using this form. Use the process described in the policy to report the issue.
Make sure you've read the documentation. Your issue may be addressed there.
Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
If possible, make a PR with a failing test to give us a starting point to work on!
Describe the bug
It seems the bridge is getting lost when using captured globals. In the following case, angle, seems to be identified as a float; the symbols table's entry, however, has its type as !cc.ptr<f64>, which is not indeed a f64. Thus the issues seems to be that the user of angle expects a value (register), while the bridge symbol table gets populated with memory.
Required prerequisites
Describe the bug
It seems the bridge is getting lost when using captured globals. In the following case,
angle
, seems to be identified as a float; the symbols table's entry, however, has its type as!cc.ptr<f64>
, which is not indeed af64
. Thus the issues seems to be that the user ofangle
expects a value (register), while the bridge symbol table gets populated with memory.Steps to reproduce the bug
Trying to run the above code.
Expected behavior
The code should run.
Is this a regression? If it is, put the last known working version (or commit) here.
Not a regression
Environment
Suggestions
No response
The text was updated successfully, but these errors were encountered: