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
use.std::math::u64
begin
push.1.0
push.2.0
exec.u64::checked_add
end
[From the manual]
Here std,math etc are identifiers. Notice no quotes around the names. Therefore they should be declared/defined somewhere. Hence I propose the MVM Assembler parser be modified to accept these "instructions" and initial just forget them:
program.name
module.libname.modname
For my research tool i will process files with multiple libraries, modules, and programs, all at once (because for testing, you don't want to stuff about with search paths and multiples files).
There is no library instruction, a library is formed implicitly by using multiple modules with the same libname.
MVM Assembler could enforce more stringent requirements. For example, using program.name allows to start checking for illegal exports.
The text was updated successfully, but these errors were encountered:
In MVM assembler you can say
[From the manual]
Here
std
,math
etc are identifiers. Notice no quotes around the names. Therefore they should be declared/defined somewhere. Hence I propose the MVM Assembler parser be modified to accept these "instructions" and initial just forget them:program.name
module.libname.modname
For my research tool i will process files with multiple libraries, modules, and programs, all at once (because for testing, you don't want to stuff about with search paths and multiples files).
There is no
library
instruction, a library is formed implicitly by using multiple modules with the samelibname
.MVM Assembler could enforce more stringent requirements. For example, using
program.name
allows to start checking for illegalexport
s.The text was updated successfully, but these errors were encountered: