Open mragonias opened 5 months ago
Dart compiler can remove dead code. If the compiler detect showLock
field is never set to true, the if block will be removed.
Dart compiler can do more interest thing such as removing unused function parameters, replace function parameter with constant if it is called only one time with a constant, inline function.
Very interesting, thank you very much for the clarification.
This is not very important, but I think that before this did not appear like this. Now in comments it always appears true even when it should appear false:
0x4dbed8: r0 = false
// 0x4dbed8: add x0, NULL, #0x30 ; true
// 0x4dbedc: StoreField: r3->field_1b = r0
// 0x4dbedc: stur w0, [x3, #0x1b]
// 0x4dbee0: r4 = true
// 0x4dbee0: add x4, NULL, #0x20 ; true
Thank for report. Fixed it.
Thank for report. Fixed it.
Still happens, 0x30 appears as a true
After git pull
, you have to run command with --rebuild
option to force rebuilding the blutter executable.
By default, the script reuses built executable if it is existed.
Hi, It works very well with blutter, but sometimes I find that information has been lost. For example in this code fragment (dart 3.1.3). As you can see in blutter, the conditional part does not appear (in bold) or perhaps it becomes very complicated to follow. (in the pp file, there is no result for showlock either)
Original
Blutter