Home
last modified time | relevance | path

Searched refs:convention (Results 1 – 25 of 203) sorted by relevance

123456789

/external/llvm/lib/Target/X86/
DX86CallingConv.td66 // X86-32 C return-value convention.
68 // The X86-32 calling convention returns FP values in ST0, unless marked
70 // weirdly; this is really the sse-regparm calling convention) in which
79 // X86-32 FastCC return-value convention.
93 // Otherwise, it is the same as the common X86 calling convention.
97 // Intel_OCL_BI return-value convention.
116 // X86-32 HiPE return-value convention.
125 // X86-64 C return-value convention.
127 // The X86-64 calling convention always returns FP values in XMM0.
136 // X86-Win64 C return-value convention.
[all …]
/external/clang/test/SemaObjC/
Darc-decls.m57 @property (retain) id newFoo; // expected-error {{property follows Cocoa naming convention for retu…
58 @property (strong) id copyBar; // expected-error {{property follows Cocoa naming convention for re…
59 @property (copy) id allocBaz; // expected-error {{property follows Cocoa naming convention for retu…
61 @property (retain) id newDFoo; // expected-error {{property follows Cocoa naming convention for ret…
62 @property (strong) id copyDBar; // expected-error {{property follows Cocoa naming convention for re…
63 @property (copy) id allocDBaz; // expected-error {{property follows Cocoa naming convention for ret…
/external/llvm/lib/Target/PowerPC/
DPPCCallingConv.td25 // Return-value convention for PowerPC
49 // Simple calling convention for 64-bit ELF PowerPC fast isel.
61 // Simple return-value convention for 64-bit ELF PowerPC fast isel.
112 // This calling convention puts vector arguments always on the stack. It is used
119 // In contrast to CC_PPC32_SVR4_VarArg, this calling convention first tries to
132 // Helper "calling convention" to handle aggregate by value arguments.
134 // of the caller. This calling convention is only used to assign those stack
140 // the CC_PPC32_SVR4 calling convention.
/external/llvm/test/CodeGen/X86/
D2009-06-12-x86_64-tail-call-conv-out-of-sync-bug.ll5 ; calling convention out of sync with standard c calling convention on x86_64)
Dghc-cc.ll3 ; Test the GHC call convention works (x86-32)
Dwin64_params.ll27 ; on other platforms here (note the x86_64_sysvcc calling convention).
/external/llvm/test/Transforms/InstCombine/
DPR7357.ll5 ; convention with a new call with a different calling convention.
/external/llvm/lib/Target/R600/
DAMDGPUCallingConv.td17 // Calling convention for SI
45 // Calling convention for R600
56 // Calling convention for compute kernels
/external/llvm/lib/Target/Hexagon/
DHexagonCallingConv.td18 // Hexagon 32-bit C return-value convention.
27 // Hexagon 32-bit C Calling convention.
/external/zlib/src/win32/
DDLL_FAQ.txt29 * The calling convention of functions is "C" (CDECL).
85 - In principle, you can do it by assigning calling convention
89 You have to find out first what kind of calling convention is
135 convention. Why not use the STDCALL convention?
136 STDCALL is the standard convention in Win32, and I need it in
139 (For readability, we use CDECL to refer to the convention
141 the convention triggered by "__stdcall", and FASTCALL to
142 refer to the convention triggered by "__fastcall".)
145 indeed the WINAPI convention (which translates to STDCALL in
163 convention used by the C compilers that run under Windows.
[all …]
/external/llvm/lib/Target/MSP430/
DREADME.txt18 2. Libcalls: multiplication, division, remainder. Note, that calling convention
19 for libcalls is incomptible with calling convention of libcalls of msp430-gcc
/external/llvm/include/llvm/Target/
DTargetCallingConv.td50 /// CCIfCC - Match if the current calling convention is 'CC'.
134 /// CCDelegateTo - This action invokes the specified sub-calling-convention. It
140 /// CallingConv - An instance of this is used to define each calling convention
147 /// convention. The order of registers is used by PrologEpilogInsertion when
/external/zlib/src/contrib/vstudio/
Dreadme.txt48 It uses the WINAPI calling convention for the exported functions, and
56 is exporting the functions using the CDECL convention. See the file
/external/libpng/projects/owatcom/
Dpngconfig.mak69 # the required change to the calling convention.
71 # By default libpng is built to use the __cdecl calling convention on
74 # the __watcall convention (compared with both MSVC and GCC which use __cdecl
148 $# of the OpenWatcom library calling convention.)
/external/llvm/lib/Target/SystemZ/
DSystemZCallingConv.td16 // z/Linux return value calling convention
46 // The convention is that true integer arguments that are smaller
DSystemZ.td29 // Calling convention description
/external/llvm/docs/
DStackMaps.rst33 convention and may return a value. They also imply stack map
85 number of arguments according to its calling convention. This allows
220 lowered according to the calling convention specified at the
222 type also return a value according to calling convention.
231 map because they are already fixed by the calling convention. The
234 convention has been introduced for use with stack maps, anyregcc,
254 in $rdi, and a return value in $rax per native calling convention:
277 sequence does not need arguments fixed to specific calling convention
278 registers, then the ``anyregcc`` convention may be used:
380 patchpoint intrinsic is used with a calling convention that by default
/external/chromium_org/third_party/cython/src/Cython/Includes/libc/
Dlocale.pxd45 # 7.11.2 Numeric formatting convention inquiry
/external/chromium_org/remoting/resources/
Dresource_ids15 # common convention starts practical use of IDs at 100 or 101.
/external/libvorbis/doc/
D02-bitpacking.tex15 convention specifies the correct mapping of the logical packet
24 purposes of the bitpacking convention, a byte implies the native,
35 convention is still well defined for any native byte size; Vorbis uses
59 The Vorbis bitpacking convention specifies storage and bitstream
/external/chromium_org/chromecast/shell/browser/resources/
Dresource_ids15 # common convention starts practical use of IDs at 100 or 101.
/external/llvm/test/Transforms/GlobalOpt/
Dfastcc.ll16 ; convention.
/external/llvm/test/CodeGen/ARM/
Dswift-vldm.ll25 ; We are relying on the calling convention and that register allocation
/external/mesa3d/src/mesa/drivers/windows/gdi/
Dmesa.def8 ; function calling convention. Microsoft's
9 ; OPENGL32 uses this convention and so must the
21 ; the decorated names, even though the calling convention
/external/chromium_org/third_party/mesa/src/src/mesa/drivers/windows/gdi/
Dmesa.def8 ; function calling convention. Microsoft's
9 ; OPENGL32 uses this convention and so must the
21 ; the decorated names, even though the calling convention

123456789