This document describes techniques for writing backends for LLVM which convert the LLVM representation to machine assembly code or other languages.

In general, you want to follow the format of SPARC, X86 or PowerPC (in lib/Target). SPARC is the simplest backend, and is RISC, so if you're working on a RISC target, it is a good one to start with.

To create a static compiler (one that emits text assembly), you need to implement the following:

• Describe the register set.
  • Create a TableGen description of the register set and register classes
  • Implement a subclass of MRegisterInfo
• Describe the instruction set.
  • Create a TableGen description of the instruction set
  • Implement a subclass of TargetInstrInfo
• Describe the target machine.
  • Create a TableGen description of the target that describes the pointer size and references the instruction set
  • Implement a subclass of TargetMachine, which configures TargetData correctly
  • Register your new target using the RegisterTarget template:
    
    

    RegisterTarget<MyTargetMachine> M("short_name", "  Target name");
    

    
    Here, MyTargetMachine is the name of your implemented subclass of TargetMachine, short_name is the option that will be active following -march= to select a target in llc and lli, and the last string is the description of your target to appear in -help listing.
• Implement the assembly printer for the architecture.
  • Define all of the assembly strings for your target, adding them to the instructions in your *InstrInfo.td file.
  • Implement the llvm::AsmPrinter interface.
• Implement an instruction selector for the architecture.
  • The recommended method is the pattern-matching DAG-to-DAG instruction selector (for example, see the PowerPC backend in PPCISelDAGtoDAG.cpp). Parts of instruction selector creation can be performed by adding patterns to the instructions in your .td file.
• Optionally, add subtarget support.
  • If your target has multiple subtargets (e.g. variants with different capabilities), implement the llvm::TargetSubtarget interface for your architecture. This allows you to add -mcpu= and -mattr= options.
• Optionally, add JIT support.
  • Create a subclass of TargetJITInfo
  • Create a machine code emitter that will be used to emit binary code directly into memory, given MachineInstrs

• TableGen register info description - describe a class which will store the register's number in the binary encoding of the instruction (e.g., for JIT purposes).

  You also need to define register classes to contain these registers, such as the integer register class and floating-point register class, so that you can allocate virtual registers to instructions from these sets, and let the target-independent register allocator automatically choose the actual architected registers.

  // class Register is defined in Target.td
  class TargetReg<string name> : Register<name> {
    let Namespace = "Target";
  }
  
  class IntReg<bits<5> num, string name> : TargetReg<name> {
    field bits<5> Num = num;
  }
  
  def R0 : IntReg<0, "%R0">;
  ...
  
  // class RegisterClass is defined in Target.td
  def IReg : RegisterClass<i64, 64, [R0, ... ]>;
  

• TableGen instruction info description - break up instructions into classes, usually that's already done by the manufacturer (see instruction manual). Define a class for each instruction category. Define each opcode as a subclass of the category, with appropriate parameters such as the fixed binary encoding of opcodes and extended opcodes, and map the register bits to the bits of the instruction which they are encoded in (for the JIT). Also specify how the instruction should be printed so it can use the automatic assembly printer, e.g.:

  // class Instruction is defined in Target.td
  class Form<bits<6> opcode, dag OL, string asmstr> : Instruction {
    field bits<42> Inst;
  
    let Namespace = "Target";
    let Inst{0-6} = opcode;
    let OperandList = OL;
    let AsmString = asmstr;
  }
  
  def ADD : Form<42, (ops IReg:$rD, IReg:$rA, IReg:$rB), "add $rD, $rA, $rB">;
  

For now, just take a look at lib/Target/CBackend for an example of how the C backend is written.

• Code generator - describes some of the classes in code generation at a high level, but it is not (yet) complete
• TableGen fundamentals - describes how to use TableGen to describe your target information succinctly
• Debugging code generation with bugpoint - shows bugpoint usage scenarios to simplify backend development