blob: 7de2d3f5eb4b56c156a8b89320fb4b5d048452cd [file] [log] [blame]
Chris Lattnerfc24e832004-08-01 03:23:34 +00001//===- Target.td - Target Independent TableGen interface ---*- tablegen -*-===//
John Criswell29265fe2003-10-21 15:17:13 +00002//
3// The LLVM Compiler Infrastructure
4//
5// This file was developed by the LLVM research group and is distributed under
6// the University of Illinois Open Source License. See LICENSE.TXT for details.
7//
8//===----------------------------------------------------------------------===//
Chris Lattner8418e362003-07-29 23:07:13 +00009//
10// This file defines the target-independent interfaces which should be
11// implemented by each target which is using a TableGen based code generator.
12//
Misha Brukmanbb053ce2003-05-29 18:48:17 +000013//===----------------------------------------------------------------------===//
14
Chris Lattnere45b6992003-07-30 05:50:12 +000015
16//===----------------------------------------------------------------------===//
17//
Chris Lattner845ed842003-07-28 04:24:59 +000018// Value types - These values correspond to the register types defined in the
Chris Lattnereaa5b962003-08-07 13:52:22 +000019// ValueTypes.h file. If you update anything here, you must update it there as
20// well!
Chris Lattner2b3ac6b2003-07-30 22:16:41 +000021//
Chris Lattnereaa5b962003-08-07 13:52:22 +000022class ValueType<int size, int value> {
23 string Namespace = "MVT";
24 int Size = size;
25 int Value = value;
26}
Chris Lattnere45b6992003-07-30 05:50:12 +000027
Chris Lattner391e9432004-02-11 03:08:45 +000028def OtherVT: ValueType<0 , 0>; // "Other" value
Chris Lattnereaa5b962003-08-07 13:52:22 +000029def i1 : ValueType<1 , 1>; // One bit boolean value
30def i8 : ValueType<8 , 2>; // 8-bit integer value
31def i16 : ValueType<16 , 3>; // 16-bit integer value
32def i32 : ValueType<32 , 4>; // 32-bit integer value
33def i64 : ValueType<64 , 5>; // 64-bit integer value
34def i128 : ValueType<128, 5>; // 128-bit integer value
35def f32 : ValueType<32 , 7>; // 32-bit floating point value
36def f64 : ValueType<64 , 8>; // 64-bit floating point value
37def f80 : ValueType<80 , 9>; // 80-bit floating point value
Chris Lattnerd24ad522005-08-25 17:07:09 +000038def f128 : ValueType<128, 10>; // 128-bit floating point value
39def FlagVT : ValueType<0 , 11>; // Condition code or machine flag
40def isVoid : ValueType<0 , 12>; // Produces no value
Chris Lattnere45b6992003-07-30 05:50:12 +000041
42//===----------------------------------------------------------------------===//
43// Register file description - These classes are used to fill in the target
Chris Lattnerd1a5bc82005-10-04 05:09:20 +000044// description classes.
Chris Lattnere45b6992003-07-30 05:50:12 +000045
Chris Lattnerd1a5bc82005-10-04 05:09:20 +000046class RegisterClass; // Forward def
Chris Lattnere45b6992003-07-30 05:50:12 +000047
Chris Lattnere8e81a22004-09-14 04:17:02 +000048// Register - You should define one instance of this class for each register
49// in the target machine. String n will become the "name" of the register.
Chris Lattner33ce5f82005-09-30 04:13:23 +000050class Register<string n> {
Misha Brukmanbb053ce2003-05-29 18:48:17 +000051 string Namespace = "";
Chris Lattnere8e81a22004-09-14 04:17:02 +000052 string Name = n;
Chris Lattner6a92fde2004-08-21 02:17:39 +000053
54 // SpillSize - If this value is set to a non-zero value, it is the size in
55 // bits of the spill slot required to hold this register. If this value is
56 // set to zero, the information is inferred from any register classes the
57 // register belongs to.
58 int SpillSize = 0;
59
60 // SpillAlignment - This value is used to specify the alignment required for
61 // spilling the register. Like SpillSize, this should only be explicitly
62 // specified if the register is not in a register class.
63 int SpillAlignment = 0;
Chris Lattner9c66ed82003-08-03 22:12:37 +000064
Chris Lattner33ce5f82005-09-30 04:13:23 +000065 // Aliases - A list of registers that this register overlaps with. A read or
66 // modification of this register can potentially read or modifie the aliased
67 // registers.
68 //
69 list<Register> Aliases = [];
Misha Brukmanbb053ce2003-05-29 18:48:17 +000070}
71
Chris Lattnere8e81a22004-09-14 04:17:02 +000072// RegisterGroup - This can be used to define instances of Register which
73// need to specify aliases.
74// List "aliases" specifies which registers are aliased to this one. This
75// allows the code generator to be careful not to put two values with
76// overlapping live ranges into registers which alias.
77class RegisterGroup<string n, list<Register> aliases> : Register<n> {
78 let Aliases = aliases;
Chris Lattnere45b6992003-07-30 05:50:12 +000079}
80
81// RegisterClass - Now that all of the registers are defined, and aliases
82// between registers are defined, specify which registers belong to which
83// register classes. This also defines the default allocation order of
84// registers by register allocators.
85//
Chris Lattner3fb85f22005-08-19 18:48:48 +000086class RegisterClass<string namespace, ValueType regType, int alignment,
87 list<Register> regList> {
88 string Namespace = namespace;
89
Chris Lattner2b3ac6b2003-07-30 22:16:41 +000090 // RegType - Specify the ValueType of the registers in this register class.
91 // Note that all registers in a register class must have the same ValueType.
92 //
Chris Lattnere45b6992003-07-30 05:50:12 +000093 ValueType RegType = regType;
Chris Lattner2b3ac6b2003-07-30 22:16:41 +000094
95 // Alignment - Specify the alignment required of the registers when they are
96 // stored or loaded to memory.
97 //
Chris Lattner75c817a2003-08-01 05:18:03 +000098 int Size = RegType.Size;
Chris Lattnere45b6992003-07-30 05:50:12 +000099 int Alignment = alignment;
Chris Lattner2b3ac6b2003-07-30 22:16:41 +0000100
101 // MemberList - Specify which registers are in this class. If the
102 // allocation_order_* method are not specified, this also defines the order of
103 // allocation used by the register allocator.
104 //
Chris Lattnere45b6992003-07-30 05:50:12 +0000105 list<Register> MemberList = regList;
Chris Lattner2b3ac6b2003-07-30 22:16:41 +0000106
Chris Lattnerbd26a822005-08-19 19:13:20 +0000107 // MethodProtos/MethodBodies - These members can be used to insert arbitrary
108 // code into a generated register class. The normal usage of this is to
109 // overload virtual methods.
110 code MethodProtos = [{}];
111 code MethodBodies = [{}];
Chris Lattnere45b6992003-07-30 05:50:12 +0000112}
113
114
115//===----------------------------------------------------------------------===//
Jim Laskey74ab9962005-10-19 19:51:16 +0000116// Pull in the common support for scheduling
117//
118include "../TargetSchedule.td"
119
120
121//===----------------------------------------------------------------------===//
Chris Lattner6a7439f2003-08-03 18:18:31 +0000122// Instruction set description - These classes correspond to the C++ classes in
123// the Target/TargetInstrInfo.h file.
Chris Lattnere45b6992003-07-30 05:50:12 +0000124//
Misha Brukmanbb053ce2003-05-29 18:48:17 +0000125class Instruction {
Chris Lattner1cabced72004-08-01 09:36:44 +0000126 string Name = ""; // The opcode string for this instruction
Misha Brukmanbb053ce2003-05-29 18:48:17 +0000127 string Namespace = "";
128
Chris Lattnerfc24e832004-08-01 03:23:34 +0000129 dag OperandList; // An dag containing the MI operand list.
Chris Lattnerfd689382004-08-01 04:40:43 +0000130 string AsmString = ""; // The .s format to print the instruction with.
Chris Lattnerfc24e832004-08-01 03:23:34 +0000131
132 // Pattern - Set to the DAG pattern for this instruction, if we know of one,
133 // otherwise, uninitialized.
134 list<dag> Pattern;
135
136 // The follow state will eventually be inferred automatically from the
137 // instruction pattern.
138
139 list<Register> Uses = []; // Default to using no non-operand registers
140 list<Register> Defs = []; // Default to modifying no non-operand registers
Misha Brukmanbb053ce2003-05-29 18:48:17 +0000141
142 // These bits capture information about the high-level semantics of the
143 // instruction.
Chris Lattner6a561be2003-07-29 23:02:49 +0000144 bit isReturn = 0; // Is this instruction a return instruction?
145 bit isBranch = 0; // Is this instruction a branch instruction?
Chris Lattner2ab11422004-07-31 02:07:07 +0000146 bit isBarrier = 0; // Can control flow fall through this instruction?
Chris Lattner6a561be2003-07-29 23:02:49 +0000147 bit isCall = 0; // Is this instruction a call instruction?
Nate Begemanc762ab72004-09-28 21:29:00 +0000148 bit isLoad = 0; // Is this instruction a load instruction?
149 bit isStore = 0; // Is this instruction a store instruction?
Chris Lattner6a561be2003-07-29 23:02:49 +0000150 bit isTwoAddress = 0; // Is this a two address instruction?
Chris Lattner182db0c2005-01-02 02:27:48 +0000151 bit isConvertibleToThreeAddress = 0; // Can this 2-addr instruction promote?
152 bit isCommutable = 0; // Is this 3 operand instruction commutable?
Chris Lattner6a561be2003-07-29 23:02:49 +0000153 bit isTerminator = 0; // Is this part of the terminator for a basic block?
Chris Lattner66522232004-09-28 18:34:14 +0000154 bit hasDelaySlot = 0; // Does this instruction have an delay slot?
Chris Lattnerc6a03382005-08-26 20:55:40 +0000155 bit usesCustomDAGSchedInserter = 0; // Pseudo instr needing special help.
Jim Laskey74ab9962005-10-19 19:51:16 +0000156
157 InstrItinClass Itinerary; // Execution steps used for scheduling.
Chris Lattner0c4dd1e2003-08-06 15:31:02 +0000158}
159
160
Chris Lattnerfd689382004-08-01 04:40:43 +0000161/// ops definition - This is just a simple marker used to identify the operands
162/// list for an instruction. This should be used like this:
163/// (ops R32:$dst, R32:$src) or something similar.
164def ops;
Chris Lattner6bd2d262004-08-11 01:53:34 +0000165
Chris Lattner5cfa3772005-08-18 23:17:07 +0000166/// variable_ops definition - Mark this instruction as taking a variable number
167/// of operands.
168def variable_ops;
169
Chris Lattner6bd2d262004-08-11 01:53:34 +0000170/// Operand Types - These provide the built-in operand types that may be used
171/// by a target. Targets can optionally provide their own operand types as
172/// needed, though this should not be needed for RISC targets.
173class Operand<ValueType ty> {
174 int NumMIOperands = 1;
175 ValueType Type = ty;
176 string PrintMethod = "printOperand";
177}
178
Chris Lattnerae0c2c752004-08-15 05:37:00 +0000179def i1imm : Operand<i1>;
Chris Lattner6bd2d262004-08-11 01:53:34 +0000180def i8imm : Operand<i8>;
181def i16imm : Operand<i16>;
182def i32imm : Operand<i32>;
183def i64imm : Operand<i64>;
Chris Lattner6a7439f2003-08-03 18:18:31 +0000184
Chris Lattner6ffa5012004-08-14 22:50:53 +0000185// InstrInfo - This class should only be instantiated once to provide parameters
186// which are global to the the target machine.
187//
188class InstrInfo {
189 Instruction PHIInst;
190
191 // If the target wants to associate some target-specific information with each
192 // instruction, it should provide these two lists to indicate how to assemble
193 // the target specific information into the 32 bits available.
194 //
195 list<string> TSFlagsFields = [];
196 list<int> TSFlagsShifts = [];
Misha Brukmandba1f62e2004-10-14 05:53:40 +0000197
198 // Target can specify its instructions in either big or little-endian formats.
199 // For instance, while both Sparc and PowerPC are big-endian platforms, the
200 // Sparc manual specifies its instructions in the format [31..0] (big), while
201 // PowerPC specifies them using the format [0..31] (little).
202 bit isLittleEndianEncoding = 0;
Chris Lattner6ffa5012004-08-14 22:50:53 +0000203}
204
205//===----------------------------------------------------------------------===//
206// AsmWriter - This class can be implemented by targets that need to customize
207// the format of the .s file writer.
208//
209// Subtargets can have multiple different asmwriters (e.g. AT&T vs Intel syntax
210// on X86 for example).
211//
212class AsmWriter {
213 // AsmWriterClassName - This specifies the suffix to use for the asmwriter
214 // class. Generated AsmWriter classes are always prefixed with the target
215 // name.
216 string AsmWriterClassName = "AsmPrinter";
217
218 // InstFormatName - AsmWriters can specify the name of the format string to
219 // print instructions with.
220 string InstFormatName = "AsmString";
Chris Lattner42c43b22004-10-03 19:34:18 +0000221
222 // Variant - AsmWriters can be of multiple different variants. Variants are
223 // used to support targets that need to emit assembly code in ways that are
224 // mostly the same for different targets, but have minor differences in
225 // syntax. If the asmstring contains {|} characters in them, this integer
226 // will specify which alternative to use. For example "{x|y|z}" with Variant
227 // == 1, will expand to "y".
228 int Variant = 0;
Chris Lattner6ffa5012004-08-14 22:50:53 +0000229}
230def DefaultAsmWriter : AsmWriter;
231
232
Chris Lattner6a7439f2003-08-03 18:18:31 +0000233//===----------------------------------------------------------------------===//
234// Target - This class contains the "global" target information
235//
236class Target {
237 // CalleeSavedRegisters - As you might guess, this is a list of the callee
238 // saved registers for a target.
239 list<Register> CalleeSavedRegisters = [];
240
241 // PointerType - Specify the value type to be used to represent pointers in
242 // this target. Typically this is an i32 or i64 type.
243 ValueType PointerType;
244
Chris Lattner6ffa5012004-08-14 22:50:53 +0000245 // InstructionSet - Instruction set description for this target.
Chris Lattner6a7439f2003-08-03 18:18:31 +0000246 InstrInfo InstructionSet;
Chris Lattner6ffa5012004-08-14 22:50:53 +0000247
Chris Lattner42c43b22004-10-03 19:34:18 +0000248 // AssemblyWriters - The AsmWriter instances available for this target.
249 list<AsmWriter> AssemblyWriters = [DefaultAsmWriter];
Misha Brukmanbb053ce2003-05-29 18:48:17 +0000250}
Chris Lattner0d74deb2003-08-04 21:07:37 +0000251
Chris Lattner0d74deb2003-08-04 21:07:37 +0000252//===----------------------------------------------------------------------===//
Jim Laskey97611002005-10-19 13:34:52 +0000253// SubtargetFeature - A characteristic of the chip set.
254//
Jim Laskey53ad1102005-10-26 17:28:23 +0000255class SubtargetFeature<string n, string t, string a, string d> {
Jim Laskey97611002005-10-19 13:34:52 +0000256 // Name - Feature name. Used by command line (-mattr=) to determine the
257 // appropriate target chip.
258 //
259 string Name = n;
260
Jim Laskey53ad1102005-10-26 17:28:23 +0000261 // Type - Type of attribute to be set by feature.
262 //
263 string Type = t;
264
265 // Attribute - Attribute to be set by feature.
266 //
267 string Attribute = a;
268
Jim Laskey97611002005-10-19 13:34:52 +0000269 // Desc - Feature description. Used by command line (-mattr=) to display help
270 // information.
271 //
272 string Desc = d;
273}
274
275//===----------------------------------------------------------------------===//
276// Processor chip sets - These values represent each of the chip sets supported
277// by the scheduler. Each Processor definition requires corresponding
278// instruction itineraries.
279//
280class Processor<string n, ProcessorItineraries pi, list<SubtargetFeature> f> {
281 // Name - Chip set name. Used by command line (-mcpu=) to determine the
282 // appropriate target chip.
283 //
284 string Name = n;
285
286 // ProcItin - The scheduling information for the target processor.
287 //
288 ProcessorItineraries ProcItin = pi;
289
290 // Features - list of
Jim Laskey9ed90322005-10-21 19:05:19 +0000291 list<SubtargetFeature> Features = f;
Jim Laskey97611002005-10-19 13:34:52 +0000292}
293
294//===----------------------------------------------------------------------===//
Chris Lattnerd83571b2005-10-10 06:00:30 +0000295// Pull in the common support for DAG isel generation
Chris Lattner0d74deb2003-08-04 21:07:37 +0000296//
Chris Lattnerd83571b2005-10-10 06:00:30 +0000297include "../TargetSelectionDAG.td"