Lines Matching refs:test

75 is NOT INCLUDED in {i,f}test.sa (an example "Call-out" section is provided at
76 the end of this file). The purpose of this section is to allow the test
80 to a function required by the test packages (these functions and their
84 sit adjacent to the {i,f}test.sa image in memory. Since itest.sa and ftest.sa
88 to access the test routines. Since the {i,f}test.sa hex files contain
95 For example, to run the 060ISP test, write a program that includes the
101 section is 128 bytes long; and the 68060ISP test entry point is located
105 the entry code jumps to the appropriate test code within the code section.
117 The test packages call _print_string() and _print_number()
120 In "C"-like fashion, the test program calls:
128 For _print_string(), the test programs pass a longword address
129 of the string on the stack. For _print_number(), the test programs pass
133 for a test package, it should flush the output so that it's not
134 buffered. In this way, if the test program crashes, at least the previous
139 0x0: integer test
143 0x00: main fp test
144 0x08: FP unimplemented test
147 The floating-point unit test has 3 entry points which will require
151 main fp test: tests (1) unimp effective address exception
163 	    _real_{snan,operr,ovfl,unfl,dz,inex}(). the test expects
166 	    alternate result, the test will print "failed" but this
172 test all 68060SP connections. For example, they do not test connections
174 will be system-implemented several different ways and the test packages
177 Example test package set-up: