Lines Matching refs:Generate
58 need to re-generate traces with real hardware; the test cases do not support
66 Note that it takes a few minutes to generate everything.
85 Each configuration file will serve to generate one or more test files,
101 An `operand` represents an argument passed to the macro-assembler to generate an
164 // Python type from `test_generator.data_types` to use to generate C++ code
181 specify what C++ code to generate in order to load and record the input value,
213 // List of files to generate.
243 We want to generate C++ code as such:
329 This will specify what C++ code to generate before and after emitting the
340 several test files. We will generate one file per element in the "test-files"
374 Above, we've decided to generate three tests: a "simulator" test and two
386 never execute anything. MacroAssembler tests currently only generate code to
388 tested. Because you may want to generate more than one test of the same type, as
398 // Generate all combinations of instructions where "rd" an "rn" are the same
422 // Generate all combinations of instructions with different condition codes.
463 // Generate 10 random instructions with all different registers but use the
495 // Generate 2000 random instructions out of all possible operand combinations.
543 generate the same code.
558 For simplicity, let's generate tests for an instruction with only `NZCV` and two
578 It will generate the following input array.
591 It will also generate a list of instructions to test:
681 help='Configuration files, each will generate a test file.')
732 # Generate code to switch instruction set.
735 # Generate code to emit instructions.
741 # Generate code to trace the execution and print C++.
744 # Generate code to compare the results against a trace.
