Both supported Teradyne platforms share the same decompiler. It’s assumed, at
this early stage, that the differences in decompiling are negligible, but
future enhancements will most likely split the two at some point.
Although all opcodes and arguments, including match loops, should decompile
correctly, they are not yet supported for execution and are simply ignored. In fact,
all opcodes (except repeat) are ignored, includingend_module.
In the source, the imports are written as type of import then name of import.
In the retuned Hash, the keys are the name of the imports and the values are the import types.
Vector
Platform Node
Description
Return Class
Default Value
Example Output
Additional Information
opcode
The opcode, if present in the vector.
String, NilClass
nil
"repeat"
N/A
opcode_arguments
Any comman-separated, opcode arguments, if present.
Array
[]
['5']
N/A
Note that repeat is actually an opcode for this platform. Many, many vectors
will have opcode and opcode_arguments that simply duplicate the generic repeat
accessor.
The V93K supports patterns of just sequencer instructions (see the approved
simple.avc pattern), which does not contain a first_vector. In such
cases, calls to many of the methods will raise an exception. For example,
calls to #add_pins, #execute, and anything on the Pinlist will fail. As
only vector support is available at the moment, there is not much that can
be done with these types of pattern anyway.
That said, these patterns can still be decompiled, with full
EnumerableExt
functionality. Any custom execution or conversion implementations, or custom
processing methods, can still be used.