blob: 573050dafd54ed776e319d5903a19b240ff50fb3 [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 Lattnerc6b13e22006-03-24 18:52:35 +000015// Include all information about LLVM intrinsics.
16include "llvm/Intrinsics.td"
Chris Lattnere45b6992003-07-30 05:50:12 +000017
18//===----------------------------------------------------------------------===//
19// Register file description - These classes are used to fill in the target
Chris Lattnerd1a5bc82005-10-04 05:09:20 +000020// description classes.
Chris Lattnere45b6992003-07-30 05:50:12 +000021
Chris Lattnerd1a5bc82005-10-04 05:09:20 +000022class RegisterClass; // Forward def
Chris Lattnere45b6992003-07-30 05:50:12 +000023
Chris Lattnere8e81a22004-09-14 04:17:02 +000024// Register - You should define one instance of this class for each register
25// in the target machine. String n will become the "name" of the register.
Chris Lattner33ce5f82005-09-30 04:13:23 +000026class Register<string n> {
Misha Brukmanbb053ce2003-05-29 18:48:17 +000027 string Namespace = "";
Chris Lattnere8e81a22004-09-14 04:17:02 +000028 string Name = n;
Chris Lattner6a92fde2004-08-21 02:17:39 +000029
30 // SpillSize - If this value is set to a non-zero value, it is the size in
31 // bits of the spill slot required to hold this register. If this value is
32 // set to zero, the information is inferred from any register classes the
33 // register belongs to.
34 int SpillSize = 0;
35
36 // SpillAlignment - This value is used to specify the alignment required for
37 // spilling the register. Like SpillSize, this should only be explicitly
38 // specified if the register is not in a register class.
39 int SpillAlignment = 0;
Chris Lattner9c66ed82003-08-03 22:12:37 +000040
Chris Lattner33ce5f82005-09-30 04:13:23 +000041 // Aliases - A list of registers that this register overlaps with. A read or
42 // modification of this register can potentially read or modifie the aliased
43 // registers.
44 //
45 list<Register> Aliases = [];
Jim Laskey3b338d52006-03-24 21:13:21 +000046
47 // DwarfNumber - Number used internally by gcc/gdb to identify the register.
48 // These values can be determined by locating the <target>.h file in the
49 // directory llvmgcc/gcc/config/<target>/ and looking for REGISTER_NAMES. The
50 // order of these names correspond to the enumeration used by gcc. A value of
51 // -1 indicates that the gcc number is undefined.
52 int DwarfNumber = -1;
Misha Brukmanbb053ce2003-05-29 18:48:17 +000053}
54
Chris Lattnere8e81a22004-09-14 04:17:02 +000055// RegisterGroup - This can be used to define instances of Register which
56// need to specify aliases.
57// List "aliases" specifies which registers are aliased to this one. This
58// allows the code generator to be careful not to put two values with
59// overlapping live ranges into registers which alias.
60class RegisterGroup<string n, list<Register> aliases> : Register<n> {
61 let Aliases = aliases;
Chris Lattnere45b6992003-07-30 05:50:12 +000062}
63
64// RegisterClass - Now that all of the registers are defined, and aliases
65// between registers are defined, specify which registers belong to which
66// register classes. This also defines the default allocation order of
67// registers by register allocators.
68//
Nate Begeman006bb042005-12-01 04:51:06 +000069class RegisterClass<string namespace, list<ValueType> regTypes, int alignment,
Chris Lattner3fb85f22005-08-19 18:48:48 +000070 list<Register> regList> {
71 string Namespace = namespace;
72
Chris Lattner215280d2006-05-14 02:05:19 +000073 // RegType - Specify the list ValueType of the registers in this register
74 // class. Note that all registers in a register class must have the same
Chris Lattnerfce45ff2006-05-15 18:35:02 +000075 // ValueTypes. This is a list because some targets permit storing different
76 // types in same register, for example vector values with 128-bit total size,
77 // but different count/size of items, like SSE on x86.
Chris Lattner2b3ac6b2003-07-30 22:16:41 +000078 //
Nate Begeman006bb042005-12-01 04:51:06 +000079 list<ValueType> RegTypes = regTypes;
80
81 // Size - Specify the spill size in bits of the registers. A default value of
82 // zero lets tablgen pick an appropriate size.
83 int Size = 0;
Chris Lattner2b3ac6b2003-07-30 22:16:41 +000084
85 // Alignment - Specify the alignment required of the registers when they are
86 // stored or loaded to memory.
87 //
Chris Lattnere45b6992003-07-30 05:50:12 +000088 int Alignment = alignment;
Chris Lattner2b3ac6b2003-07-30 22:16:41 +000089
90 // MemberList - Specify which registers are in this class. If the
91 // allocation_order_* method are not specified, this also defines the order of
92 // allocation used by the register allocator.
93 //
Chris Lattnere45b6992003-07-30 05:50:12 +000094 list<Register> MemberList = regList;
Chris Lattner2b3ac6b2003-07-30 22:16:41 +000095
Chris Lattnerbd26a822005-08-19 19:13:20 +000096 // MethodProtos/MethodBodies - These members can be used to insert arbitrary
97 // code into a generated register class. The normal usage of this is to
98 // overload virtual methods.
99 code MethodProtos = [{}];
100 code MethodBodies = [{}];
Chris Lattnere45b6992003-07-30 05:50:12 +0000101}
102
103
104//===----------------------------------------------------------------------===//
Jim Laskey3b338d52006-03-24 21:13:21 +0000105// DwarfRegNum - This class provides a mapping of the llvm register enumeration
106// to the register numbering used by gcc and gdb. These values are used by a
107// debug information writer (ex. DwarfWriter) to describe where values may be
108// located during execution.
109class DwarfRegNum<int N> {
110 // DwarfNumber - Number used internally by gcc/gdb to identify the register.
111 // These values can be determined by locating the <target>.h file in the
112 // directory llvmgcc/gcc/config/<target>/ and looking for REGISTER_NAMES. The
113 // order of these names correspond to the enumeration used by gcc. A value of
114 // -1 indicates that the gcc number is undefined.
115 int DwarfNumber = N;
116}
117
118//===----------------------------------------------------------------------===//
Jim Laskey74ab9962005-10-19 19:51:16 +0000119// Pull in the common support for scheduling
120//
Vladimir Prus788db2c2006-05-16 06:39:36 +0000121include "TargetSchedule.td"
Jim Laskey74ab9962005-10-19 19:51:16 +0000122
Evan Chengd296a432005-12-14 22:02:59 +0000123class Predicate; // Forward def
Jim Laskey74ab9962005-10-19 19:51:16 +0000124
125//===----------------------------------------------------------------------===//
Chris Lattner6a7439f2003-08-03 18:18:31 +0000126// Instruction set description - These classes correspond to the C++ classes in
127// the Target/TargetInstrInfo.h file.
Chris Lattnere45b6992003-07-30 05:50:12 +0000128//
Misha Brukmanbb053ce2003-05-29 18:48:17 +0000129class Instruction {
Chris Lattner1cabced72004-08-01 09:36:44 +0000130 string Name = ""; // The opcode string for this instruction
Misha Brukmanbb053ce2003-05-29 18:48:17 +0000131 string Namespace = "";
132
Chris Lattnerfc24e832004-08-01 03:23:34 +0000133 dag OperandList; // An dag containing the MI operand list.
Chris Lattnerfd689382004-08-01 04:40:43 +0000134 string AsmString = ""; // The .s format to print the instruction with.
Chris Lattnerfc24e832004-08-01 03:23:34 +0000135
136 // Pattern - Set to the DAG pattern for this instruction, if we know of one,
137 // otherwise, uninitialized.
138 list<dag> Pattern;
139
140 // The follow state will eventually be inferred automatically from the
141 // instruction pattern.
142
143 list<Register> Uses = []; // Default to using no non-operand registers
144 list<Register> Defs = []; // Default to modifying no non-operand registers
Misha Brukmanbb053ce2003-05-29 18:48:17 +0000145
Evan Chengd296a432005-12-14 22:02:59 +0000146 // Predicates - List of predicates which will be turned into isel matching
147 // code.
148 list<Predicate> Predicates = [];
149
Evan Chengc767acd2006-07-19 00:24:41 +0000150 // Code size.
151 int CodeSize = 0;
152
Evan Cheng52df7402006-04-19 20:38:28 +0000153 // Added complexity passed onto matching pattern.
154 int AddedComplexity = 0;
Evan Chengaa3325e2006-04-19 18:07:24 +0000155
Misha Brukmanbb053ce2003-05-29 18:48:17 +0000156 // These bits capture information about the high-level semantics of the
157 // instruction.
Chris Lattner6a561be2003-07-29 23:02:49 +0000158 bit isReturn = 0; // Is this instruction a return instruction?
159 bit isBranch = 0; // Is this instruction a branch instruction?
Chris Lattner2ab11422004-07-31 02:07:07 +0000160 bit isBarrier = 0; // Can control flow fall through this instruction?
Chris Lattner6a561be2003-07-29 23:02:49 +0000161 bit isCall = 0; // Is this instruction a call instruction?
Nate Begemanc762ab72004-09-28 21:29:00 +0000162 bit isLoad = 0; // Is this instruction a load instruction?
163 bit isStore = 0; // Is this instruction a store instruction?
Chris Lattner6a561be2003-07-29 23:02:49 +0000164 bit isTwoAddress = 0; // Is this a two address instruction?
Chris Lattner182db0c2005-01-02 02:27:48 +0000165 bit isConvertibleToThreeAddress = 0; // Can this 2-addr instruction promote?
166 bit isCommutable = 0; // Is this 3 operand instruction commutable?
Chris Lattner6a561be2003-07-29 23:02:49 +0000167 bit isTerminator = 0; // Is this part of the terminator for a basic block?
Chris Lattner66522232004-09-28 18:34:14 +0000168 bit hasDelaySlot = 0; // Does this instruction have an delay slot?
Chris Lattnerc6a03382005-08-26 20:55:40 +0000169 bit usesCustomDAGSchedInserter = 0; // Pseudo instr needing special help.
Evan Chenge8531382005-12-04 08:13:17 +0000170 bit hasCtrlDep = 0; // Does this instruction r/w ctrl-flow chains?
Evan Cheng14c53b42005-12-26 09:11:45 +0000171 bit noResults = 0; // Does this instruction produce no results?
Jim Laskey74ab9962005-10-19 19:51:16 +0000172
Chris Lattner12405742006-01-27 01:46:15 +0000173 InstrItinClass Itinerary = NoItinerary;// Execution steps used for scheduling.
Evan Cheng7a6a5b92006-11-01 00:26:27 +0000174
175 string Constraints = "";
Chris Lattner0c4dd1e2003-08-06 15:31:02 +0000176}
177
Chris Lattneradcaf292006-10-12 17:49:27 +0000178/// Imp - Helper class for specifying the implicit uses/defs set for an
179/// instruction.
180class Imp<list<Register> uses, list<Register> defs> {
181 list<Register> Uses = uses;
182 list<Register> Defs = defs;
183}
184
Evan Chengd296a432005-12-14 22:02:59 +0000185/// Predicates - These are extra conditionals which are turned into instruction
186/// selector matching code. Currently each predicate is just a string.
187class Predicate<string cond> {
188 string CondString = cond;
189}
190
191class Requires<list<Predicate> preds> {
192 list<Predicate> Predicates = preds;
193}
Chris Lattner0c4dd1e2003-08-06 15:31:02 +0000194
Chris Lattnerfd689382004-08-01 04:40:43 +0000195/// ops definition - This is just a simple marker used to identify the operands
196/// list for an instruction. This should be used like this:
197/// (ops R32:$dst, R32:$src) or something similar.
198def ops;
Chris Lattner6bd2d262004-08-11 01:53:34 +0000199
Chris Lattner5cfa3772005-08-18 23:17:07 +0000200/// variable_ops definition - Mark this instruction as taking a variable number
201/// of operands.
202def variable_ops;
203
Evan Chengf3cbd7e2006-05-18 20:44:26 +0000204/// ptr_rc definition - Mark this operand as being a pointer value whose
205/// register class is resolved dynamically via a callback to TargetInstrInfo.
206/// FIXME: We should probably change this to a class which contain a list of
207/// flags. But currently we have but one flag.
208def ptr_rc;
209
Chris Lattner6bd2d262004-08-11 01:53:34 +0000210/// Operand Types - These provide the built-in operand types that may be used
211/// by a target. Targets can optionally provide their own operand types as
212/// needed, though this should not be needed for RISC targets.
213class Operand<ValueType ty> {
Chris Lattner6bd2d262004-08-11 01:53:34 +0000214 ValueType Type = ty;
215 string PrintMethod = "printOperand";
Chris Lattner252d88c2005-11-19 07:00:10 +0000216 int NumMIOperands = 1;
217 dag MIOperandInfo = (ops);
Chris Lattner6bd2d262004-08-11 01:53:34 +0000218}
219
Chris Lattnerae0c2c752004-08-15 05:37:00 +0000220def i1imm : Operand<i1>;
Chris Lattner6bd2d262004-08-11 01:53:34 +0000221def i8imm : Operand<i8>;
222def i16imm : Operand<i16>;
223def i32imm : Operand<i32>;
224def i64imm : Operand<i64>;
Chris Lattner6a7439f2003-08-03 18:18:31 +0000225
Chris Lattner6ffa5012004-08-14 22:50:53 +0000226// InstrInfo - This class should only be instantiated once to provide parameters
227// which are global to the the target machine.
228//
229class InstrInfo {
Chris Lattner6ffa5012004-08-14 22:50:53 +0000230 // If the target wants to associate some target-specific information with each
231 // instruction, it should provide these two lists to indicate how to assemble
232 // the target specific information into the 32 bits available.
233 //
234 list<string> TSFlagsFields = [];
235 list<int> TSFlagsShifts = [];
Misha Brukmandba1f62e2004-10-14 05:53:40 +0000236
237 // Target can specify its instructions in either big or little-endian formats.
238 // For instance, while both Sparc and PowerPC are big-endian platforms, the
239 // Sparc manual specifies its instructions in the format [31..0] (big), while
240 // PowerPC specifies them using the format [0..31] (little).
241 bit isLittleEndianEncoding = 0;
Chris Lattner6ffa5012004-08-14 22:50:53 +0000242}
243
Chris Lattner12405742006-01-27 01:46:15 +0000244// Standard Instructions.
245def PHI : Instruction {
246 let OperandList = (ops variable_ops);
247 let AsmString = "PHINODE";
Chris Lattner85e99092006-05-01 17:00:49 +0000248 let Namespace = "TargetInstrInfo";
Chris Lattner12405742006-01-27 01:46:15 +0000249}
250def INLINEASM : Instruction {
251 let OperandList = (ops variable_ops);
252 let AsmString = "";
Chris Lattner85e99092006-05-01 17:00:49 +0000253 let Namespace = "TargetInstrInfo";
Chris Lattner12405742006-01-27 01:46:15 +0000254}
255
Chris Lattner6ffa5012004-08-14 22:50:53 +0000256//===----------------------------------------------------------------------===//
257// AsmWriter - This class can be implemented by targets that need to customize
258// the format of the .s file writer.
259//
260// Subtargets can have multiple different asmwriters (e.g. AT&T vs Intel syntax
261// on X86 for example).
262//
263class AsmWriter {
264 // AsmWriterClassName - This specifies the suffix to use for the asmwriter
265 // class. Generated AsmWriter classes are always prefixed with the target
266 // name.
267 string AsmWriterClassName = "AsmPrinter";
268
269 // InstFormatName - AsmWriters can specify the name of the format string to
270 // print instructions with.
271 string InstFormatName = "AsmString";
Chris Lattner42c43b22004-10-03 19:34:18 +0000272
273 // Variant - AsmWriters can be of multiple different variants. Variants are
274 // used to support targets that need to emit assembly code in ways that are
275 // mostly the same for different targets, but have minor differences in
276 // syntax. If the asmstring contains {|} characters in them, this integer
277 // will specify which alternative to use. For example "{x|y|z}" with Variant
278 // == 1, will expand to "y".
279 int Variant = 0;
Chris Lattner6ffa5012004-08-14 22:50:53 +0000280}
281def DefaultAsmWriter : AsmWriter;
282
283
Chris Lattner6a7439f2003-08-03 18:18:31 +0000284//===----------------------------------------------------------------------===//
285// Target - This class contains the "global" target information
286//
287class Target {
Chris Lattner6ffa5012004-08-14 22:50:53 +0000288 // InstructionSet - Instruction set description for this target.
Chris Lattner6a7439f2003-08-03 18:18:31 +0000289 InstrInfo InstructionSet;
Chris Lattner6ffa5012004-08-14 22:50:53 +0000290
Chris Lattner42c43b22004-10-03 19:34:18 +0000291 // AssemblyWriters - The AsmWriter instances available for this target.
292 list<AsmWriter> AssemblyWriters = [DefaultAsmWriter];
Misha Brukmanbb053ce2003-05-29 18:48:17 +0000293}
Chris Lattner0d74deb2003-08-04 21:07:37 +0000294
Chris Lattner0d74deb2003-08-04 21:07:37 +0000295//===----------------------------------------------------------------------===//
Jim Laskey97611002005-10-19 13:34:52 +0000296// SubtargetFeature - A characteristic of the chip set.
297//
Evan Chengd98701c2006-01-27 08:09:42 +0000298class SubtargetFeature<string n, string a, string v, string d> {
Jim Laskey97611002005-10-19 13:34:52 +0000299 // Name - Feature name. Used by command line (-mattr=) to determine the
300 // appropriate target chip.
301 //
302 string Name = n;
303
Jim Laskey53ad1102005-10-26 17:28:23 +0000304 // Attribute - Attribute to be set by feature.
305 //
306 string Attribute = a;
307
Evan Chengd98701c2006-01-27 08:09:42 +0000308 // Value - Value the attribute to be set to by feature.
309 //
310 string Value = v;
311
Jim Laskey97611002005-10-19 13:34:52 +0000312 // Desc - Feature description. Used by command line (-mattr=) to display help
313 // information.
314 //
315 string Desc = d;
316}
317
318//===----------------------------------------------------------------------===//
319// Processor chip sets - These values represent each of the chip sets supported
320// by the scheduler. Each Processor definition requires corresponding
321// instruction itineraries.
322//
323class Processor<string n, ProcessorItineraries pi, list<SubtargetFeature> f> {
324 // Name - Chip set name. Used by command line (-mcpu=) to determine the
325 // appropriate target chip.
326 //
327 string Name = n;
328
329 // ProcItin - The scheduling information for the target processor.
330 //
331 ProcessorItineraries ProcItin = pi;
332
333 // Features - list of
Jim Laskey9ed90322005-10-21 19:05:19 +0000334 list<SubtargetFeature> Features = f;
Jim Laskey97611002005-10-19 13:34:52 +0000335}
336
337//===----------------------------------------------------------------------===//
Chris Lattnerd83571b2005-10-10 06:00:30 +0000338// Pull in the common support for DAG isel generation
Chris Lattner0d74deb2003-08-04 21:07:37 +0000339//
Vladimir Prus788db2c2006-05-16 06:39:36 +0000340include "TargetSelectionDAG.td"