mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2025-01-20 12:31:40 +00:00
86245071b5
Print the range of registers used with a single letter prefix. This better matches what the shader compiler produces and is overall less obnoxious than concatenating all of the subregister names together. Instead of SGPR0, it will print s0. Instead of SGPR0_SGPR1, it will print s[0:1] and so on. There doesn't appear to be a straightforward way to get the actual register info in the InstPrinter, so this parses the generated name to print with the new syntax. The required test changes are pretty nasty, and register matching regexes are now worse. Since there isn't a way to add to a variable in FileCheck, some of the tests now don't check the exact number of registers used, but I don't think that will be a real problem. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@194443 91177308-0d34-0410-b5e6-96231b3b80d8
+==============================================================================+ | 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.