blob: 5747ac38d9b2a2dfaef6d767ae42236947225b16 [file] [log] [blame]
Chris Lattnerbbe664c2004-08-01 03:23:34 +00001//===- Target.td - Target Independent TableGen interface ---*- tablegen -*-===//
John Criswell856ba762003-10-21 15:17:13 +00002//
3// The LLVM Compiler Infrastructure
4//
Chris Lattner4ee451d2007-12-29 20:36:04 +00005// This file is distributed under the University of Illinois Open Source
6// License. See LICENSE.TXT for details.
John Criswell856ba762003-10-21 15:17:13 +00007//
8//===----------------------------------------------------------------------===//
Chris Lattneree6b5f62003-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 Brukman01c16382003-05-29 18:48:17 +000013//===----------------------------------------------------------------------===//
14
Chris Lattnerda10f192006-03-24 18:52:35 +000015// Include all information about LLVM intrinsics.
16include "llvm/Intrinsics.td"
Chris Lattner7c289522003-07-30 05:50:12 +000017
18//===----------------------------------------------------------------------===//
19// Register file description - These classes are used to fill in the target
Chris Lattnerccc8ed72005-10-04 05:09:20 +000020// description classes.
Chris Lattner7c289522003-07-30 05:50:12 +000021
Chris Lattnerccc8ed72005-10-04 05:09:20 +000022class RegisterClass; // Forward def
Chris Lattner7c289522003-07-30 05:50:12 +000023
Chris Lattnerb2286572004-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 Lattneref242b12005-09-30 04:13:23 +000026class Register<string n> {
Misha Brukman01c16382003-05-29 18:48:17 +000027 string Namespace = "";
Chris Lattnerb2286572004-09-14 04:17:02 +000028 string Name = n;
Chris Lattnerb4d83c12004-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 Lattner76bf8682003-08-03 22:12:37 +000040
Chris Lattneref242b12005-09-30 04:13:23 +000041 // Aliases - A list of registers that this register overlaps with. A read or
Dan Gohmane26bff22007-02-20 20:52:03 +000042 // modification of this register can potentially read or modify the aliased
Chris Lattneref242b12005-09-30 04:13:23 +000043 // registers.
Chris Lattneref242b12005-09-30 04:13:23 +000044 list<Register> Aliases = [];
Jim Laskey8da17b22006-03-24 21:13:21 +000045
Evan Cheng3cafbf72007-04-20 21:13:46 +000046 // SubRegs - A list of registers that are parts of this register. Note these
47 // are "immediate" sub-registers and the registers within the list do not
48 // themselves overlap. e.g. For X86, EAX's SubRegs list contains only [AX],
49 // not [AX, AH, AL].
50 list<Register> SubRegs = [];
51
Anton Korobeynikovf191c802007-11-11 19:50:10 +000052 // DwarfNumbers - Numbers used internally by gcc/gdb to identify the register.
Jim Laskey8da17b22006-03-24 21:13:21 +000053 // These values can be determined by locating the <target>.h file in the
54 // directory llvmgcc/gcc/config/<target>/ and looking for REGISTER_NAMES. The
55 // order of these names correspond to the enumeration used by gcc. A value of
Anton Korobeynikov2e7eedf2007-11-11 19:53:50 +000056 // -1 indicates that the gcc number is undefined and -2 that register number
57 // is invalid for this mode/flavour.
Anton Korobeynikovf191c802007-11-11 19:50:10 +000058 list<int> DwarfNumbers = [];
Misha Brukman01c16382003-05-29 18:48:17 +000059}
60
Evan Cheng3cafbf72007-04-20 21:13:46 +000061// RegisterWithSubRegs - This can be used to define instances of Register which
62// need to specify sub-registers.
63// List "subregs" specifies which registers are sub-registers to this one. This
64// is used to populate the SubRegs and AliasSet fields of TargetRegisterDesc.
65// This allows the code generator to be careful not to put two values with
66// overlapping live ranges into registers which alias.
67class RegisterWithSubRegs<string n, list<Register> subregs> : Register<n> {
68 let SubRegs = subregs;
69}
70
Nate Begeman7bf1c272007-05-01 05:57:02 +000071// SubRegSet - This can be used to define a specific mapping of registers to
72// indices, for use as named subregs of a particular physical register. Each
73// register in 'subregs' becomes an addressable subregister at index 'n' of the
74// corresponding register in 'regs'.
75class SubRegSet<int n, list<Register> regs, list<Register> subregs> {
76 int index = n;
77
78 list<Register> From = regs;
79 list<Register> To = subregs;
Chris Lattner7c289522003-07-30 05:50:12 +000080}
81
82// RegisterClass - Now that all of the registers are defined, and aliases
83// between registers are defined, specify which registers belong to which
84// register classes. This also defines the default allocation order of
85// registers by register allocators.
86//
Nate Begeman6510b222005-12-01 04:51:06 +000087class RegisterClass<string namespace, list<ValueType> regTypes, int alignment,
Chris Lattner1ff95402005-08-19 18:48:48 +000088 list<Register> regList> {
89 string Namespace = namespace;
90
Chris Lattner506efda2006-05-14 02:05:19 +000091 // RegType - Specify the list ValueType of the registers in this register
92 // class. Note that all registers in a register class must have the same
Chris Lattner94ae9d32006-05-15 18:35:02 +000093 // ValueTypes. This is a list because some targets permit storing different
94 // types in same register, for example vector values with 128-bit total size,
95 // but different count/size of items, like SSE on x86.
Chris Lattner0ad13612003-07-30 22:16:41 +000096 //
Nate Begeman6510b222005-12-01 04:51:06 +000097 list<ValueType> RegTypes = regTypes;
98
99 // Size - Specify the spill size in bits of the registers. A default value of
100 // zero lets tablgen pick an appropriate size.
101 int Size = 0;
Chris Lattner0ad13612003-07-30 22:16:41 +0000102
103 // Alignment - Specify the alignment required of the registers when they are
104 // stored or loaded to memory.
105 //
Chris Lattner7c289522003-07-30 05:50:12 +0000106 int Alignment = alignment;
Chris Lattner0ad13612003-07-30 22:16:41 +0000107
Evan Chenga3ca3142007-09-19 01:35:01 +0000108 // CopyCost - This value is used to specify the cost of copying a value
109 // between two registers in this register class. The default value is one
110 // meaning it takes a single instruction to perform the copying. A negative
111 // value means copying is extremely expensive or impossible.
112 int CopyCost = 1;
113
Chris Lattner0ad13612003-07-30 22:16:41 +0000114 // MemberList - Specify which registers are in this class. If the
115 // allocation_order_* method are not specified, this also defines the order of
116 // allocation used by the register allocator.
117 //
Chris Lattner7c289522003-07-30 05:50:12 +0000118 list<Register> MemberList = regList;
Christopher Lamba3211252007-06-13 22:20:15 +0000119
120 // SubClassList - Specify which register classes correspond to subregisters
121 // of this class. The order should be by subregister set index.
122 list<RegisterClass> SubRegClassList = [];
Chris Lattner0ad13612003-07-30 22:16:41 +0000123
Chris Lattnerecbce612005-08-19 19:13:20 +0000124 // MethodProtos/MethodBodies - These members can be used to insert arbitrary
125 // code into a generated register class. The normal usage of this is to
126 // overload virtual methods.
127 code MethodProtos = [{}];
128 code MethodBodies = [{}];
Chris Lattner7c289522003-07-30 05:50:12 +0000129}
130
131
132//===----------------------------------------------------------------------===//
Jim Laskey8da17b22006-03-24 21:13:21 +0000133// DwarfRegNum - This class provides a mapping of the llvm register enumeration
134// to the register numbering used by gcc and gdb. These values are used by a
135// debug information writer (ex. DwarfWriter) to describe where values may be
136// located during execution.
Anton Korobeynikovf191c802007-11-11 19:50:10 +0000137class DwarfRegNum<list<int> Numbers> {
138 // DwarfNumbers - Numbers used internally by gcc/gdb to identify the register.
Jim Laskey8da17b22006-03-24 21:13:21 +0000139 // These values can be determined by locating the <target>.h file in the
140 // directory llvmgcc/gcc/config/<target>/ and looking for REGISTER_NAMES. The
141 // order of these names correspond to the enumeration used by gcc. A value of
Anton Korobeynikov2e7eedf2007-11-11 19:53:50 +0000142 // -1 indicates that the gcc number is undefined and -2 that register number is
143 // invalid for this mode/flavour.
Anton Korobeynikovf191c802007-11-11 19:50:10 +0000144 list<int> DwarfNumbers = Numbers;
Jim Laskey8da17b22006-03-24 21:13:21 +0000145}
146
147//===----------------------------------------------------------------------===//
Jim Laskey53842142005-10-19 19:51:16 +0000148// Pull in the common support for scheduling
149//
Vladimir Pruse438c2a2006-05-16 06:39:36 +0000150include "TargetSchedule.td"
Jim Laskey53842142005-10-19 19:51:16 +0000151
Evan Cheng58e84a62005-12-14 22:02:59 +0000152class Predicate; // Forward def
Jim Laskey53842142005-10-19 19:51:16 +0000153
154//===----------------------------------------------------------------------===//
Chris Lattnera5100d92003-08-03 18:18:31 +0000155// Instruction set description - These classes correspond to the C++ classes in
156// the Target/TargetInstrInfo.h file.
Chris Lattner7c289522003-07-30 05:50:12 +0000157//
Misha Brukman01c16382003-05-29 18:48:17 +0000158class Instruction {
Chris Lattner33c23dd2004-08-01 09:36:44 +0000159 string Name = ""; // The opcode string for this instruction
Misha Brukman01c16382003-05-29 18:48:17 +0000160 string Namespace = "";
161
Evan Cheng64d80e32007-07-19 01:14:50 +0000162 dag OutOperandList; // An dag containing the MI def operand list.
163 dag InOperandList; // An dag containing the MI use operand list.
Chris Lattnerc1392032004-08-01 04:40:43 +0000164 string AsmString = ""; // The .s format to print the instruction with.
Chris Lattnerbbe664c2004-08-01 03:23:34 +0000165
166 // Pattern - Set to the DAG pattern for this instruction, if we know of one,
167 // otherwise, uninitialized.
168 list<dag> Pattern;
169
170 // The follow state will eventually be inferred automatically from the
171 // instruction pattern.
172
173 list<Register> Uses = []; // Default to using no non-operand registers
174 list<Register> Defs = []; // Default to modifying no non-operand registers
Misha Brukman01c16382003-05-29 18:48:17 +0000175
Evan Cheng58e84a62005-12-14 22:02:59 +0000176 // Predicates - List of predicates which will be turned into isel matching
177 // code.
178 list<Predicate> Predicates = [];
179
Evan Chenge6f32032006-07-19 00:24:41 +0000180 // Code size.
181 int CodeSize = 0;
182
Evan Chengf5e1dc22006-04-19 20:38:28 +0000183 // Added complexity passed onto matching pattern.
184 int AddedComplexity = 0;
Evan Cheng59413202006-04-19 18:07:24 +0000185
Misha Brukman01c16382003-05-29 18:48:17 +0000186 // These bits capture information about the high-level semantics of the
187 // instruction.
Chris Lattner84c40c12003-07-29 23:02:49 +0000188 bit isReturn = 0; // Is this instruction a return instruction?
189 bit isBranch = 0; // Is this instruction a branch instruction?
Owen Anderson20ab2902007-11-12 07:39:39 +0000190 bit isIndirectBranch = 0; // Is this instruction an indirect branch?
Chris Lattner2a809f62004-07-31 02:07:07 +0000191 bit isBarrier = 0; // Can control flow fall through this instruction?
Chris Lattner84c40c12003-07-29 23:02:49 +0000192 bit isCall = 0; // Is this instruction a call instruction?
Nate Begeman8d5c5032004-09-28 21:29:00 +0000193 bit isLoad = 0; // Is this instruction a load instruction?
194 bit isStore = 0; // Is this instruction a store instruction?
Evan Cheng6e141fd2007-12-12 23:12:09 +0000195 bit isImplicitDef = 0; // Is this instruction an implicit def instruction?
Chris Lattner84c40c12003-07-29 23:02:49 +0000196 bit isTwoAddress = 0; // Is this a two address instruction?
Chris Lattner273f2282005-01-02 02:27:48 +0000197 bit isConvertibleToThreeAddress = 0; // Can this 2-addr instruction promote?
198 bit isCommutable = 0; // Is this 3 operand instruction commutable?
Chris Lattner84c40c12003-07-29 23:02:49 +0000199 bit isTerminator = 0; // Is this part of the terminator for a basic block?
Dan Gohmand45eddd2007-06-26 00:48:07 +0000200 bit isReMaterializable = 0; // Is this instruction re-materializable?
Evan Cheng064d7cd2007-05-16 20:47:01 +0000201 bit isPredicable = 0; // Is this instruction predicable?
Chris Lattner7baaf092004-09-28 18:34:14 +0000202 bit hasDelaySlot = 0; // Does this instruction have an delay slot?
Chris Lattnere3cbf822005-08-26 20:55:40 +0000203 bit usesCustomDAGSchedInserter = 0; // Pseudo instr needing special help.
Evan Chengf8ac8142005-12-04 08:13:17 +0000204 bit hasCtrlDep = 0; // Does this instruction r/w ctrl-flow chains?
Evan Chengeaa91b02007-06-19 01:26:51 +0000205 bit isNotDuplicable = 0; // Is it unsafe to duplicate this instruction?
Bill Wendling6b1da9c2007-12-14 01:48:59 +0000206
207 // Side effect flags - If neither of these flags is set, then the instruction
Bill Wendling7d9e97c2007-12-17 21:02:07 +0000208 // *always* has side effects. When set, the flags have these meanings:
209 //
210 // neverHasSideEffects - The instruction has no side effects that are not
211 // captured by any operands of the instruction or other flags, and when
212 // *all* instances of the instruction of that opcode have no side effects.
213 // mayHaveSideEffects - Some instances of the instruction can have side
214 // effects. The virtual method "isReallySideEffectFree" is called to
215 // determine this. Load instructions are an example of where this is
216 // useful. In general, loads always have side effects. However, loads from
217 // constant pools don't. Individual back ends make this determination.
218 bit neverHasSideEffects = 0;
219 bit mayHaveSideEffects = 0;
Jim Laskey53842142005-10-19 19:51:16 +0000220
Chris Lattnercedc6f42006-01-27 01:46:15 +0000221 InstrItinClass Itinerary = NoItinerary;// Execution steps used for scheduling.
Evan Cheng2f15c062006-11-01 00:26:27 +0000222
Evan Chenge77d10d2007-01-12 07:25:16 +0000223 string Constraints = ""; // OperandConstraint, e.g. $src = $dst.
Chris Lattnerfa326c72006-11-15 22:55:04 +0000224
225 /// DisableEncoding - List of operand names (e.g. "$op1,$op2") that should not
226 /// be encoded into the output machineinstr.
227 string DisableEncoding = "";
Chris Lattner3e77d6e2003-08-06 15:31:02 +0000228}
229
Evan Cheng58e84a62005-12-14 22:02:59 +0000230/// Predicates - These are extra conditionals which are turned into instruction
231/// selector matching code. Currently each predicate is just a string.
232class Predicate<string cond> {
233 string CondString = cond;
234}
235
Chris Lattnera7ad3d12007-05-03 00:27:11 +0000236/// NoHonorSignDependentRounding - This predicate is true if support for
237/// sign-dependent-rounding is not enabled.
238def NoHonorSignDependentRounding
239 : Predicate<"!HonorSignDependentRoundingFPMath()">;
240
Evan Cheng58e84a62005-12-14 22:02:59 +0000241class Requires<list<Predicate> preds> {
242 list<Predicate> Predicates = preds;
243}
Chris Lattner3e77d6e2003-08-06 15:31:02 +0000244
Chris Lattnerc1392032004-08-01 04:40:43 +0000245/// ops definition - This is just a simple marker used to identify the operands
Evan Cheng64d80e32007-07-19 01:14:50 +0000246/// list for an instruction. outs and ins are identical both syntatically and
247/// semantically, they are used to define def operands and use operands to
248/// improve readibility. This should be used like this:
249/// (outs R32:$dst), (ins R32:$src1, R32:$src2) or something similar.
Chris Lattnerc1392032004-08-01 04:40:43 +0000250def ops;
Evan Cheng64d80e32007-07-19 01:14:50 +0000251def outs;
252def ins;
Chris Lattner52d2f142004-08-11 01:53:34 +0000253
Chris Lattner329cdc32005-08-18 23:17:07 +0000254/// variable_ops definition - Mark this instruction as taking a variable number
255/// of operands.
256def variable_ops;
257
Evan Chengffd43642006-05-18 20:44:26 +0000258/// ptr_rc definition - Mark this operand as being a pointer value whose
259/// register class is resolved dynamically via a callback to TargetInstrInfo.
260/// FIXME: We should probably change this to a class which contain a list of
261/// flags. But currently we have but one flag.
262def ptr_rc;
263
Chris Lattner52d2f142004-08-11 01:53:34 +0000264/// Operand Types - These provide the built-in operand types that may be used
265/// by a target. Targets can optionally provide their own operand types as
266/// needed, though this should not be needed for RISC targets.
267class Operand<ValueType ty> {
Chris Lattner52d2f142004-08-11 01:53:34 +0000268 ValueType Type = ty;
269 string PrintMethod = "printOperand";
Chris Lattnerbe7a2ff2005-11-19 07:00:10 +0000270 dag MIOperandInfo = (ops);
Chris Lattner52d2f142004-08-11 01:53:34 +0000271}
272
Chris Lattnerfa146832004-08-15 05:37:00 +0000273def i1imm : Operand<i1>;
Chris Lattner52d2f142004-08-11 01:53:34 +0000274def i8imm : Operand<i8>;
275def i16imm : Operand<i16>;
276def i32imm : Operand<i32>;
277def i64imm : Operand<i64>;
Chris Lattnera5100d92003-08-03 18:18:31 +0000278
Evan Cheng2aa133e2007-07-05 07:09:09 +0000279/// zero_reg definition - Special node to stand for the zero register.
280///
281def zero_reg;
Chris Lattner60a09a52006-11-03 23:52:18 +0000282
283/// PredicateOperand - This can be used to define a predicate operand for an
284/// instruction. OpTypes specifies the MIOperandInfo for the operand, and
285/// AlwaysVal specifies the value of this predicate when set to "always
Evan Cheng49ce02e2007-07-06 23:21:02 +0000286/// execute".
Evan Cheng2aa133e2007-07-05 07:09:09 +0000287class PredicateOperand<ValueType ty, dag OpTypes, dag AlwaysVal>
288 : Operand<ty> {
Chris Lattner60a09a52006-11-03 23:52:18 +0000289 let MIOperandInfo = OpTypes;
Evan Chenge496d782007-07-06 01:00:16 +0000290 dag DefaultOps = AlwaysVal;
Chris Lattner60a09a52006-11-03 23:52:18 +0000291}
292
Evan Chenge496d782007-07-06 01:00:16 +0000293/// OptionalDefOperand - This is used to define a optional definition operand
294/// for an instruction. DefaultOps is the register the operand represents if none
295/// is supplied, e.g. zero_reg.
296class OptionalDefOperand<ValueType ty, dag OpTypes, dag defaultops>
297 : Operand<ty> {
298 let MIOperandInfo = OpTypes;
299 dag DefaultOps = defaultops;
Evan Cheng2aa133e2007-07-05 07:09:09 +0000300}
301
Chris Lattner60a09a52006-11-03 23:52:18 +0000302
Chris Lattner175580c2004-08-14 22:50:53 +0000303// InstrInfo - This class should only be instantiated once to provide parameters
304// which are global to the the target machine.
305//
306class InstrInfo {
Chris Lattner175580c2004-08-14 22:50:53 +0000307 // If the target wants to associate some target-specific information with each
308 // instruction, it should provide these two lists to indicate how to assemble
309 // the target specific information into the 32 bits available.
310 //
311 list<string> TSFlagsFields = [];
312 list<int> TSFlagsShifts = [];
Misha Brukman99ee67a2004-10-14 05:53:40 +0000313
314 // Target can specify its instructions in either big or little-endian formats.
315 // For instance, while both Sparc and PowerPC are big-endian platforms, the
316 // Sparc manual specifies its instructions in the format [31..0] (big), while
317 // PowerPC specifies them using the format [0..31] (little).
318 bit isLittleEndianEncoding = 0;
Chris Lattner175580c2004-08-14 22:50:53 +0000319}
320
Chris Lattnercedc6f42006-01-27 01:46:15 +0000321// Standard Instructions.
322def PHI : Instruction {
Evan Cheng64d80e32007-07-19 01:14:50 +0000323 let OutOperandList = (ops);
324 let InOperandList = (ops variable_ops);
Chris Lattnercedc6f42006-01-27 01:46:15 +0000325 let AsmString = "PHINODE";
Chris Lattnerde321a82006-05-01 17:00:49 +0000326 let Namespace = "TargetInstrInfo";
Chris Lattnercedc6f42006-01-27 01:46:15 +0000327}
328def INLINEASM : Instruction {
Evan Cheng64d80e32007-07-19 01:14:50 +0000329 let OutOperandList = (ops);
330 let InOperandList = (ops variable_ops);
Chris Lattnercedc6f42006-01-27 01:46:15 +0000331 let AsmString = "";
Chris Lattnerde321a82006-05-01 17:00:49 +0000332 let Namespace = "TargetInstrInfo";
Chris Lattnercedc6f42006-01-27 01:46:15 +0000333}
Jim Laskey1ee29252007-01-26 14:34:52 +0000334def LABEL : Instruction {
Evan Cheng64d80e32007-07-19 01:14:50 +0000335 let OutOperandList = (ops);
336 let InOperandList = (ops i32imm:$id);
Jim Laskey1ee29252007-01-26 14:34:52 +0000337 let AsmString = "";
338 let Namespace = "TargetInstrInfo";
339 let hasCtrlDep = 1;
340}
Christopher Lamb08d52072007-07-26 07:48:21 +0000341def EXTRACT_SUBREG : Instruction {
342 let OutOperandList = (ops variable_ops);
343 let InOperandList = (ops variable_ops);
344 let AsmString = "";
345 let Namespace = "TargetInstrInfo";
346}
347def INSERT_SUBREG : Instruction {
348 let OutOperandList = (ops variable_ops);
349 let InOperandList = (ops variable_ops);
350 let AsmString = "";
351 let Namespace = "TargetInstrInfo";
352}
Chris Lattnercedc6f42006-01-27 01:46:15 +0000353
Chris Lattner175580c2004-08-14 22:50:53 +0000354//===----------------------------------------------------------------------===//
355// AsmWriter - This class can be implemented by targets that need to customize
356// the format of the .s file writer.
357//
358// Subtargets can have multiple different asmwriters (e.g. AT&T vs Intel syntax
359// on X86 for example).
360//
361class AsmWriter {
362 // AsmWriterClassName - This specifies the suffix to use for the asmwriter
363 // class. Generated AsmWriter classes are always prefixed with the target
364 // name.
365 string AsmWriterClassName = "AsmPrinter";
366
367 // InstFormatName - AsmWriters can specify the name of the format string to
368 // print instructions with.
369 string InstFormatName = "AsmString";
Chris Lattner0fa20662004-10-03 19:34:18 +0000370
371 // Variant - AsmWriters can be of multiple different variants. Variants are
372 // used to support targets that need to emit assembly code in ways that are
373 // mostly the same for different targets, but have minor differences in
374 // syntax. If the asmstring contains {|} characters in them, this integer
375 // will specify which alternative to use. For example "{x|y|z}" with Variant
376 // == 1, will expand to "y".
377 int Variant = 0;
Chris Lattner175580c2004-08-14 22:50:53 +0000378}
379def DefaultAsmWriter : AsmWriter;
380
381
Chris Lattnera5100d92003-08-03 18:18:31 +0000382//===----------------------------------------------------------------------===//
383// Target - This class contains the "global" target information
384//
385class Target {
Chris Lattner175580c2004-08-14 22:50:53 +0000386 // InstructionSet - Instruction set description for this target.
Chris Lattnera5100d92003-08-03 18:18:31 +0000387 InstrInfo InstructionSet;
Chris Lattner175580c2004-08-14 22:50:53 +0000388
Chris Lattner0fa20662004-10-03 19:34:18 +0000389 // AssemblyWriters - The AsmWriter instances available for this target.
390 list<AsmWriter> AssemblyWriters = [DefaultAsmWriter];
Misha Brukman01c16382003-05-29 18:48:17 +0000391}
Chris Lattner244883e2003-08-04 21:07:37 +0000392
Chris Lattner244883e2003-08-04 21:07:37 +0000393//===----------------------------------------------------------------------===//
Jim Laskey0de87962005-10-19 13:34:52 +0000394// SubtargetFeature - A characteristic of the chip set.
395//
Bill Wendling4222d802007-05-04 20:38:40 +0000396class SubtargetFeature<string n, string a, string v, string d,
397 list<SubtargetFeature> i = []> {
Jim Laskey0de87962005-10-19 13:34:52 +0000398 // Name - Feature name. Used by command line (-mattr=) to determine the
399 // appropriate target chip.
400 //
401 string Name = n;
402
Jim Laskeyf0c2be42005-10-26 17:28:23 +0000403 // Attribute - Attribute to be set by feature.
404 //
405 string Attribute = a;
406
Evan Cheng19c95502006-01-27 08:09:42 +0000407 // Value - Value the attribute to be set to by feature.
408 //
409 string Value = v;
410
Jim Laskey0de87962005-10-19 13:34:52 +0000411 // Desc - Feature description. Used by command line (-mattr=) to display help
412 // information.
413 //
414 string Desc = d;
Bill Wendling4222d802007-05-04 20:38:40 +0000415
416 // Implies - Features that this feature implies are present. If one of those
417 // features isn't set, then this one shouldn't be set either.
418 //
419 list<SubtargetFeature> Implies = i;
Jim Laskey0de87962005-10-19 13:34:52 +0000420}
421
422//===----------------------------------------------------------------------===//
423// Processor chip sets - These values represent each of the chip sets supported
424// by the scheduler. Each Processor definition requires corresponding
425// instruction itineraries.
426//
427class Processor<string n, ProcessorItineraries pi, list<SubtargetFeature> f> {
428 // Name - Chip set name. Used by command line (-mcpu=) to determine the
429 // appropriate target chip.
430 //
431 string Name = n;
432
433 // ProcItin - The scheduling information for the target processor.
434 //
435 ProcessorItineraries ProcItin = pi;
436
437 // Features - list of
Jim Laskeyf5fc2cb2005-10-21 19:05:19 +0000438 list<SubtargetFeature> Features = f;
Jim Laskey0de87962005-10-19 13:34:52 +0000439}
440
441//===----------------------------------------------------------------------===//
Chris Lattnerd637a8b2007-02-27 06:59:52 +0000442// Pull in the common support for calling conventions.
443//
444include "TargetCallingConv.td"
445
446//===----------------------------------------------------------------------===//
447// Pull in the common support for DAG isel generation.
Chris Lattner244883e2003-08-04 21:07:37 +0000448//
Vladimir Pruse438c2a2006-05-16 06:39:36 +0000449include "TargetSelectionDAG.td"