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
ASMOP pseudo op-code for hex-defined opcodes, which will handle cell overflows (in contrast with naive definitions like int sqr (int x) asm "x{20A8} s,";)
Better handling of impossible op-code params, for instance throwing error in case 256 PUSHPOW2 instead of substituting it with PUSHNAN
Recursive <{ ... }>c to allow #compile "jetton_wallet.func" to jetton_wallet_code; cell literals. Probably it is expedient to merge extended_fift branch first and use anonymous namespaces.
Introduce Asm.fif versioning, so funC may inject restrictions on used Asm.fif version
PUSHSLICE for slices with high number of bits/refs e3af63e
muldivc
)int sqr (int x) asm "x{20A8} s,";
)RSHIFT#MOD
,RSHIFTMOD
,MULRSHIFT#MOD
,MULRSHIFTMOD
,LSHIFT#DIVMOD
,LSHIFT#DIVMODR
,RSHIFT#MOD
,RSHIFTR#MOD
,MULRSHIFTR#MOD
,LSHIFTDIVMODR
256 PUSHPOW2
instead of substituting it withPUSHNAN
<{ ... }>c
to allow#compile "jetton_wallet.func" to jetton_wallet_code;
cell literals. Probably it is expedient to merge extended_fift branch first and use anonymous namespaces.Asm.fif
versioning, so funC may inject restrictions on usedAsm.fif
versionPUSHSLICE
for slices with high number of bits/refs e3af63eThe text was updated successfully, but these errors were encountered: