While this project explicitly targets Falcon v5 at the moment, we will want to support v0, v3, v4 and v6 at some point in the future. The most notable difference between these versions is that either some instructions did not exist at all or different types of encoding were used.
Thus, we will want faucon-asm-derive to accept a version attribute in its Instruction derive macro which allows for filtering out specific variants of the InstructionKind macro in correlance with the given version bitmask. Since faucon always depends on a configuration file no matter what command is invoked, the desired MCU revision can be extracted from there and then be used for instruction lookup.
While this project explicitly targets Falcon v5 at the moment, we will want to support v0, v3, v4 and v6 at some point in the future. The most notable difference between these versions is that either some instructions did not exist at all or different types of encoding were used.
Thus, we will want
faucon-asm-deriveto accept aversionattribute in itsInstructionderive macro which allows for filtering out specific variants of theInstructionKindmacro in correlance with the given version bitmask. Sincefauconalways depends on a configuration file no matter what command is invoked, the desired MCU revision can be extracted from there and then be used for instruction lookup.