Open MetalPizzaCat opened 2 years ago
Closed by mistake
This is caused by ProcessOperation
, because =
is treated as oepration where left side uses &a
and right side uses &b
and during preparation phase it calles mov a,b
despite result being in &a
should produce this asm code
but instead produces this, probably due to wrong offset in byte code