8 9 t integer 0 10 y z integer 100 12 for i1 to x 13 t t dtoix y2

# 8 9 t integer 0 10 y z integer 100 12 for i1 to x 13

This preview shows page 299 - 304 out of 332 pages.

8 | { 9 | t : integer = 0; 10 | y : integer = 10; 11 | z : integer = 100; 12 | for ( i=1 to x) { --> 13 | t = t + dtoi((x * y**2) / z); 14 | } 15 | t = dtoi(t / x); 16 | note (" f2(3) = "+ t); 17 | } ICVD>> fin test.rs:16 f2(3) = 3 15 | t = dtoi(t / x); 16 | note (" f2(3) = "+ t); 17 | } 18 | xx:integer; 19 | f2(3); --> 20 | note("end. "); In this example, the run continues to until a breakpoint is encountered. ICVD>> fin test.rs:11 fibonacci(16) = 1597 6 | for (i in 2 thru 19) { 7 | f.push_back(f[i-2] + f[i-1]); 8 | } 9 | 10 | for (i in 0 thru 19) { B --> 11 | note("fibonacci(" + i + ") = " + f[i]); 12 | } Breakpoint #2, _MAIN_() at test.rs:11 ICVD>> fin test.rs:11 fibonacci(17) = 2584 6 | for (i in 2 thru 19) { 7 | f.push_back(f[i-2] + f[i-1]); 8 | } 9 | 10 | for (i in 0 thru 19) { B --> 11 | note("fibonacci(" + i + ") = " + f[i]); 12 | } Breakpoint #2, _MAIN_() at test.rs:11 ICVD>>
Appendix D: IC Validator PXL Debugger PXL Debugger Commands D-12 IC Validator User Guide K-2015.06 IC Validator User Guide Version K-2015.06 info break The info break command lists out information about the breakpoints set during the PXL Debugger session. There are two ways to list the breakpoint information: 1. info break When specified without a breakpoint number, all breakpoints are listed. ICVD>> info b Breakpoint #1, _MAIN_() at test.rs:7 Enabled Breakpoint #2, _MAIN_() at test.rs:16 Enabled 2. info break number If a breakpoint number is specified, only the breakpoint information for it is listed. ICVD>> info b 2 Breakpoint #2, _MAIN_() at test.rs:16 Enabled ICVD>>
Appendix D: IC Validator PXL Debugger PXL Debugger Commands D-13 IC Validator User Guide Version K-2015.06 list The list command list lines from the source code. There are four ways to list lines: 1. list When specified without any option, the command lists 10 lines from the last printed line. 1 | #include <math.rh> 2 | #include <diagnostics.rh> 3 | --> 4 | f: list of integer = {1, 1}; 5 | 6 | for (i in 2 thru 19) { 7 | f.push_back(f[i-2] + f[i-1]); 8 | } ICVD>> list 9 | 10 | /* comment 1 11 | comment 2 12 | comment 3 13 | comment 4 14 | comment 5 15 | */ 16 | 17 | for (i in 0 thru 19) { 18 | note("fibonacci(" + i + ") = " + f[i]); ICVD>> 2. list line Print outs, from the current file, five lines before and four lines after the specified line number. 3. list file : line Print outs, from the specified file, five lines before and four lines after the specified line number. ICVD>> list test.rs:4 1 | #include <math.rh> 2 | #include <diagnostics.rh> 3 | --> 4 | f: list of integer = {1, 1}; 5 | 6 | for (i in 2 thru 19) { 7 | f.push_back(f[i-2] + f[i-1]); 8 | } ICVD>> 4. list function
Appendix D: IC Validator PXL Debugger PXL Debugger Commands D-14 IC Validator User Guide K-2015.06 IC Validator User Guide Version K-2015.06 Prints out five lines before and four lines after the first executable line within the specified function. ICVD>> list f2 4 | 5 | f2 : function ( 6 | x : integer 7 | ) returning void 8 | { 9 | t : integer = 0; 10 | y : integer = 10; 11 | z : integer = 100; 12 | for ( i=1 to x) { 13 | t = t + dtoi((x * y**2) / z); ICVD>>
Appendix D: IC Validator PXL Debugger PXL Debugger Commands D-15 IC Validator User Guide Version K-2015.06 next The next command moves the PXL Debugger prompt to the next executable line in the runset. A next on a function call completes function execution, and then moves to the next executable line in the runset.

#### You've reached the end of your free preview.

Want to read all 332 pages?

• Fall '18
• Electronic design automation, The Run, Data-flow analysis, Definite assignment analysis, IC Validator