Commit | Line | Data |
---|---|---|
252b5132 RH |
1 | Notes on how the HPPA testsuite is organized: |
2 | ||
3 | basic.parse -- this directory contains the basic instruction parsing | |
4 | tests and a simple .stab parsing test. This would be where you'd | |
5 | add code to make sure new instructions are parsed correctly, new | |
6 | completers (such as cache hits) are parsed correctly, etc. | |
7 | ||
8 | It's also a reasonable place to make sure parsing of the various | |
9 | assembler directives is handled correctly. If you're going to add | |
10 | such code, try to be reasonably complete. Add test code for each | |
11 | basic directive and test all (or a noteworthy) subset of arguments. | |
12 | ||
13 | It should only be necessary to have an assembler to run these tests; | |
14 | calling objdump_start or something similar should not be done from | |
15 | this directory. | |
16 | ||
17 | ||
18 | more.parse -- this is where you should put additional parsing tests, such | |
19 | as tests to check mode selector parsing, string parsing, expression parsing, | |
20 | etc. It's also a reasonable place to put parsing tests which are not complete | |
21 | enough (whatever that means) for basic.parse. | |
22 | ||
23 | It should only be necessary to have an assembler to run these tests; | |
24 | calling objdump_start or something similar should not be done from | |
25 | this directory. | |
26 | ||
27 | ||
28 | reloc -- this is where you tests which examine relocations produced | |
29 | by GAS belong. To run these tests you must have a functioning objdump. | |
30 | ||
31 | ||
32 | unsorted -- this is where everything else goes. As groups of related tests | |
33 | end up in this directory, they should be broken out into a new class of | |
34 | tests. |