1*9880d681SAndroid Build Coastguard Worker+==============================================================================+ 2*9880d681SAndroid Build Coastguard Worker| How to organize the lit tests | 3*9880d681SAndroid Build Coastguard Worker+==============================================================================+ 4*9880d681SAndroid Build Coastguard Worker 5*9880d681SAndroid Build Coastguard Worker- If you write a test for matching a single DAG opcode or intrinsic, it should 6*9880d681SAndroid Build Coastguard Worker go in a file called {opcode_name,intrinsic_name}.ll (e.g. fadd.ll) 7*9880d681SAndroid Build Coastguard Worker 8*9880d681SAndroid Build Coastguard Worker- If you write a test that matches several DAG opcodes and checks for a single 9*9880d681SAndroid Build Coastguard Worker ISA instruction, then that test should go in a file called {ISA_name}.ll (e.g. 10*9880d681SAndroid Build Coastguard Worker bfi_int.ll 11*9880d681SAndroid Build Coastguard Worker 12*9880d681SAndroid Build Coastguard Worker- For all other tests, use your best judgement for organizing tests and naming 13*9880d681SAndroid Build Coastguard Worker the files. 14*9880d681SAndroid Build Coastguard Worker 15*9880d681SAndroid Build Coastguard Worker+==============================================================================+ 16*9880d681SAndroid Build Coastguard Worker| Naming conventions | 17*9880d681SAndroid Build Coastguard Worker+==============================================================================+ 18*9880d681SAndroid Build Coastguard Worker 19*9880d681SAndroid Build Coastguard Worker- Use dash '-' and not underscore '_' to separate words in file names, unless 20*9880d681SAndroid Build Coastguard Worker the file is named after a DAG opcode or ISA instruction that has an 21*9880d681SAndroid Build Coastguard Worker underscore '_' in its name. 22