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
I was poking around the Dead Cells bytecode with the GUI and noticed that a lot of functions seemed to cut off at a certain depth, even though the opcodes still had more instructions - so I wrote a small test class:
classNested {
staticfunctionmain() {
varb=512.0;
while (b>5) {
b/=2;
if (b<10) {
while (b<100) {
b*=2;
if (b>50) {
break;
}
}
}
}
}
}
Once decompiled, it yields the following output:
classNested {
staticfunctionmain() {
varb=512;
while ([nocondition]) {
b=b/2;
while ([nocondition]) {
b=b*2;
break;
}
}
}
}
I assume the [no condition] blocks are a separate issue - but the lack of nesting beyond a certain point is far more concerning when it comes to the overall accuracy of the decompilation.
The text was updated successfully, but these errors were encountered:
I was poking around the Dead Cells bytecode with the GUI and noticed that a lot of functions seemed to cut off at a certain depth, even though the opcodes still had more instructions - so I wrote a small test class:
Once decompiled, it yields the following output:
I assume the
[no condition]
blocks are a separate issue - but the lack of nesting beyond a certain point is far more concerning when it comes to the overall accuracy of the decompilation.The text was updated successfully, but these errors were encountered: