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
The function Squint.c :: rename_register1() does literal constant optimizations, and is currently unsafe. I suggest commenting out that optimization until this ticket is closed.
This bug might only occur for chained literal constant assignment:
a = b = c = 0.0;
In the case of chained literal assignment, a workaround is likely as easy as:
a = 0.0;
b = 0.0;
c = 0.0;
This bug gives me an excuse to refactor how I handle literal constants in general (which are tricky on ARM since they are embedded in inactive parts of the instruction stream). Sorry that I am not doing a more direct fix, but I do not yet have any heavy users of Squint.c .
Since I am currently in the midst of a serious medical issue, I may not have the energy to get to this for at least several more weeks.
The text was updated successfully, but these errors were encountered:
The function Squint.c :: rename_register1() does literal constant optimizations, and is currently unsafe. I suggest commenting out that optimization until this ticket is closed.
This bug might only occur for chained literal constant assignment:
a = b = c = 0.0;
In the case of chained literal assignment, a workaround is likely as easy as:
a = 0.0;
b = 0.0;
c = 0.0;
This bug gives me an excuse to refactor how I handle literal constants in general (which are tricky on ARM since they are embedded in inactive parts of the instruction stream). Sorry that I am not doing a more direct fix, but I do not yet have any heavy users of Squint.c .
Since I am currently in the midst of a serious medical issue, I may not have the energy to get to this for at least several more weeks.
The text was updated successfully, but these errors were encountered: