PPCCallingConv.td revision 2a9ddfb903ae3baede7282348afae1f750905248
1//===- PPCCallingConv.td - Calling Conventions for PowerPC ------*- C++ -*-===//
2// 
3//                     The LLVM Compiler Infrastructure
4//
5// This file is distributed under the University of Illinois Open Source
6// License. See LICENSE.TXT for details.
7// 
8//===----------------------------------------------------------------------===//
9//
10// This describes the calling conventions for the PowerPC 32- and 64-bit
11// architectures.
12//
13//===----------------------------------------------------------------------===//
14
15/// CCIfSubtarget - Match if the current subtarget has a feature F.
16class CCIfSubtarget<string F, CCAction A>
17 : CCIf<!strconcat("State.getTarget().getSubtarget<PPCSubtarget>().", F), A>;
18
19//===----------------------------------------------------------------------===//
20// Return Value Calling Convention
21//===----------------------------------------------------------------------===//
22
23// Return-value convention for PowerPC
24def RetCC_PPC : CallingConv<[
25  CCIfType<[i32], CCAssignToReg<[R3, R4, R5, R6, R7, R8, R9, R10]>>,
26  CCIfType<[i64], CCAssignToReg<[X3, X4, X5, X6]>>,
27  
28  CCIfType<[f32], CCAssignToReg<[F1]>>,
29  CCIfType<[f64], CCAssignToReg<[F1, F2]>>,
30  
31  // Vector types are always returned in V2.
32  CCIfType<[v16i8, v8i16, v4i32, v4f32], CCAssignToReg<[V2]>>
33]>;
34
35
36//===----------------------------------------------------------------------===//
37// PowerPC Argument Calling Conventions
38//===----------------------------------------------------------------------===//
39/*
40def CC_PPC : CallingConv<[
41  // The first 8 integer arguments are passed in integer registers.
42  CCIfType<[i32], CCAssignToReg<[R3, R4, R5, R6, R7, R8, R9, R10]>>,
43  CCIfType<[i64], CCAssignToReg<[X3, X4, X5, X6, X7, X8, X9, X10]>>,
44  
45  // Common sub-targets passes FP values in F1 - F13
46  CCIfType<[f32, f64], 
47           CCAssignToReg<[F1, F2, F3, F4, F5, F6, F7, F8,F9,F10,F11,F12,F13]>>,
48           
49  // The first 12 Vector arguments are passed in altivec registers.
50  CCIfType<[v16i8, v8i16, v4i32, v4f32],
51              CCAssignToReg<[V2, V3, V4, V5, V6, V7, V8, V9, V10,V11,V12,V13]>>
52
53/*
54  // Integer/FP values get stored in stack slots that are 8 bytes in size and
55  // 8-byte aligned if there are no more registers to hold them.
56  CCIfType<[i32, i64, f32, f64], CCAssignToStack<8, 8>>,
57  
58  // Vectors get 16-byte stack slots that are 16-byte aligned.
59  CCIfType<[v16i8, v8i16, v4i32, v2i64, v4f32, v2f64],
60              CCAssignToStack<16, 16>>*/
61]>;
62
63*/
64
65//===----------------------------------------------------------------------===//
66// PowerPC System V Release 4 ABI
67//===----------------------------------------------------------------------===//
68
69// _Complex arguments are never split, thus their two scalars are either
70// passed both in argument registers or both on the stack. Also _Complex
71// arguments are always passed in general purpose registers, never in
72// Floating-point registers or vector registers. Arguments which should go
73// on the stack are marked with the inreg parameter attribute.
74// Giving inreg this target-dependent (and counter-intuitive) meaning
75// simplifies things, because functions calls are not always coming from the
76// frontend but are also created implicitly e.g. for libcalls. If inreg would
77// actually mean that the argument is passed in a register, then all places
78// which create function calls/function definitions implicitly would need to
79// be aware of this fact and would need to mark arguments accordingly. With
80// inreg meaning that the argument is passed on the stack, this is not an
81// issue, except for calls which involve _Complex types.
82
83def CC_PPC_SVR4_Common : CallingConv<[
84  // The ABI requires i64 to be passed in two adjacent registers with the first
85  // register having an odd register number.
86  CCIfType<[i32], CCIfSplit<CCCustom<"CC_PPC_SVR4_Custom_AlignArgRegs">>>,
87
88  // The first 8 integer arguments are passed in integer registers.
89  CCIfType<[i32], CCIf<"!ArgFlags.isInReg()",
90    CCAssignToReg<[R3, R4, R5, R6, R7, R8, R9, R10]>>>,
91
92  // Make sure the i64 words from a long double are either both passed in
93  // registers or both passed on the stack.
94  CCIfType<[f64], CCIfSplit<CCCustom<"CC_PPC_SVR4_Custom_AlignFPArgRegs">>>,
95  
96  // FP values are passed in F1 - F8.
97  CCIfType<[f32, f64], CCAssignToReg<[F1, F2, F3, F4, F5, F6, F7, F8]>>,
98
99  // Split arguments have an alignment of 8 bytes on the stack.
100  CCIfType<[i32], CCIfSplit<CCAssignToStack<4, 8>>>,
101  
102  CCIfType<[i32], CCAssignToStack<4, 4>>,
103  
104  // Floats are stored in double precision format, thus they have the same
105  // alignment and size as doubles.
106  CCIfType<[f32,f64], CCAssignToStack<8, 8>>,  
107
108  // Vectors get 16-byte stack slots that are 16-byte aligned.
109  CCIfType<[v16i8, v8i16, v4i32, v4f32], CCAssignToStack<16, 16>>
110]>;
111
112// This calling convention puts vector arguments always on the stack. It is used
113// to assign vector arguments which belong to the variable portion of the
114// parameter list of a variable argument function.
115def CC_PPC_SVR4_VarArg : CallingConv<[
116  CCDelegateTo<CC_PPC_SVR4_Common>
117]>;
118
119// In contrast to CC_PPC_SVR4_VarArg, this calling convention first tries to put
120// vector arguments in vector registers before putting them on the stack.
121def CC_PPC_SVR4 : CallingConv<[
122  // The first 12 Vector arguments are passed in AltiVec registers.
123  CCIfType<[v16i8, v8i16, v4i32, v4f32],
124           CCAssignToReg<[V2, V3, V4, V5, V6, V7, V8, V9, V10, V11, V12, V13]>>,
125           
126  CCDelegateTo<CC_PPC_SVR4_Common>
127]>;  
128
129// Helper "calling convention" to handle aggregate by value arguments.
130// Aggregate by value arguments are always placed in the local variable space
131// of the caller. This calling convention is only used to assign those stack
132// offsets in the callers stack frame.
133//
134// Still, the address of the aggregate copy in the callers stack frame is passed
135// in a GPR (or in the parameter list area if all GPRs are allocated) from the
136// caller to the callee. The location for the address argument is assigned by
137// the CC_PPC_SVR4 calling convention.
138//
139// The only purpose of CC_PPC_SVR4_Custom_Dummy is to skip arguments which are
140// not passed by value.
141 
142def CC_PPC_SVR4_ByVal : CallingConv<[
143  CCIfByVal<CCPassByVal<4, 4>>,
144  
145  CCCustom<"CC_PPC_SVR4_Custom_Dummy">
146]>;
147
148