llvm-6502/test/CodeGen/R600
2013-05-03 17:21:31 +00:00
..
128bit-kernel-args.ll
add.ll
alu-split.ll
and.ll
bfi_int.ll
cf_end.ll
dagcombiner-bug-illegal-vec4-int-to-fp.ll
disconnected-predset-break-bug.ll
elf.ll
elf.r600.ll
fabs.ll
fadd.ll
fcmp-cnd.ll
fcmp-cnde-int-args.ll
fcmp.ll
fdiv.ll
floor.ll
fmad.ll
fmax.ll
fmin.ll
fmul.ll
fmul.v4f32.ll
fp_to_sint.ll
fp_to_uint.ll
fsub.ll
i8-to-double-to-float.ll
icmp-select-sete-reverse-args.ll
imm.ll
jump-address.ll
kcache-fold.ll
legalizedag-bug-expand-setcc.ll
lit.local.cfg
literals.ll
llvm.AMDGPU.mul.ll
llvm.AMDGPU.tex.ll
llvm.AMDGPU.trunc.ll
llvm.cos.ll
llvm.pow.ll
llvm.SI.fs.interp.constant.ll
llvm.SI.sample.ll
llvm.sin.ll
load.ll
loop-address.ll
lshl.ll
lshr.ll
mulhu.ll
or.ll R600: Expand vector or, shl, srl, and xor nodes 2013-05-03 17:21:31 +00:00
predicates.ll
pv.ll
README
reciprocal.ll
schedule-fs-loop-nested-if.ll
schedule-fs-loop-nested.ll
schedule-fs-loop.ll
schedule-if-2.ll
schedule-if.ll
schedule-vs-if-nested-loop.ll
sdiv.ll
selectcc-cnd.ll
selectcc-cnde-int.ll
selectcc-icmp-select-float.ll
selectcc-opt.ll
set-dx10.ll
setcc.ll
seto.ll
setuo.ll
shl.ll R600: Expand vector or, shl, srl, and xor nodes 2013-05-03 17:21:31 +00:00
short-args.ll
sint_to_fp.ll
srl.ll R600: Expand vector or, shl, srl, and xor nodes 2013-05-03 17:21:31 +00:00
store.ll
store.r600.ll
udiv.ll
uint_to_fp.ll
unsupported-cc.ll
urecip.ll
urem.ll
xor.ll R600: Expand vector or, shl, srl, and xor nodes 2013-05-03 17:21:31 +00:00

+==============================================================================+
| How to organize the lit tests                                                |
+==============================================================================+

- If you write a test for matching a single DAG opcode or intrinsic, it should
  go in a file called {opcode_name,intrinsic_name}.ll (e.g. fadd.ll)

- If you write a test that matches several DAG opcodes and checks for a single
  ISA instruction, then that test should go in a file called {ISA_name}.ll (e.g.
  bfi_int.ll

- For all other tests, use your best judgement for organizing tests and naming
  the files.

+==============================================================================+
| Naming conventions                                                           |
+==============================================================================+

- Use dash '-' and not underscore '_' to separate words in file names, unless
  the file is named after a DAG opcode or ISA instruction that has an
  underscore '_' in its name.