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
The C0 -> BC0 compiler will reuse the elements in local variable array when possible. This means that a same element (index) in the local variable array may have different name and type during the runtime.
Specifically, suppose some variable x is declared in a scope and some other new variable y is declared after the scope x is in, the cc0 compiler will reuse the local variable array index for x previously to store value of y.
To Reproduce
Steps to reproduce the behavior:
Compile the code below
Set breakpoint on the line that contains int[] K = array_copy(...)
Run the program
In tabular debugger (and also graphical), the variable should have name J instead of i, which is already out of scope.
Describe the bug
The C0 -> BC0 compiler will reuse the elements in local variable array when possible. This means that a same element (index) in the local variable array may have different name and type during the runtime.
Specifically, suppose some variable
x
is declared in a scope and some other new variabley
is declared after the scopex
is in, the cc0 compiler will reuse the local variable array index forx
previously to store value ofy
.To Reproduce
Steps to reproduce the behavior:
int[] K = array_copy(...)
J
instead ofi
, which is already out of scope.Expected behavior
As described above.
Screenshots
Code being executed
Additional Context
(N/A)
-This bug is reported by Prof. Iliano
The text was updated successfully, but these errors were encountered: