| /netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/M68k/ |
| H A D | M68kCallingConv.td | 15 // TODO Verify C convention follows SysV M68K ABI
29 /// M68k C return convention.
39 /// M68k fastcc return convention.
40 /// This convention allows to return up to 16 bytes in registers which can be
51 /// This is the root return-value convention for the M68k backend.
103 /// This is the root argument convention for the M68k backend.
|
| /netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/BPF/ |
| H A D | BPFCallingConv.td | 13 // BPF 64-bit C return-value convention.
16 // BPF 64-bit C Calling convention.
28 // Return-value convention when -mattr=+alu32 enabled
34 // Calling convention when -mattr=+alu32 enabled
|
| /netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/PowerPC/ |
| H A D | PPCCallingConv.td | 36 // PPC64 AnyReg return-value convention. No explicit register is specified for
40 // This calling convention is currently only supported by the stackmap and
42 // builds. On Release builds we fallback to the PPC C calling convention.
47 // Return-value convention for PowerPC coldcc.
69 // Return-value convention for PowerPC
105 // No explicit register is specified for the AnyReg calling convention. The
108 // This calling convention is currently only supported by the stackmap and
110 // builds. On Release builds we fallback to the PPC C calling convention.
120 // Simple calling convention for 64-bit ELF PowerPC fast isel.
135 // Simple return-value convention for 64-bit ELF PowerPC fast isel.
[all …]
|
| /netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/X86/ |
| H A D | X86CallingConv.td | 74 // X86-64 Intel regcall calling convention.
260 // X86-32 C return-value convention.
262 // The X86-32 calling convention returns FP values in FP0, unless marked
264 // weirdly; this is really the sse-regparm calling convention) in which
273 // X86-32 FastCC return-value convention.
287 // Otherwise, it is the same as the common X86 calling convention.
291 // Intel_OCL_BI return-value convention.
310 // X86-32 HiPE return-value convention.
319 // X86-32 Vectorcall return-value convention.
329 // X86-64 C return-value convention.
[all …]
|
| /netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/AVR/ |
| H A D | AVRCallingConv.td | 9 // Normal functions use a special calling convention, solved in code.
16 // Special return value calling convention for runtime functions.
29 // Calling convention for variadic functions.
|
| /netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/Lanai/ |
| H A D | LanaiCallingConv.td | 17 // Lanai 32-bit C Calling convention.
30 // Lanai 32-bit Fast Calling convention.
42 // Lanai 32-bit C return-value convention.
|
| /netbsd-src/external/gpl3/binutils/dist/zlib/win32/ |
| H A D | DLL_FAQ.txt | 29 * 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 …]
|
| /netbsd-src/external/gpl3/gdb.old/dist/zlib/win32/ |
| H A D | DLL_FAQ.txt | 29 * 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 …]
|
| /netbsd-src/external/gpl3/binutils.old/dist/zlib/win32/ |
| H A D | DLL_FAQ.txt | 29 * 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 …]
|
| /netbsd-src/external/gpl3/gdb/dist/zlib/win32/ |
| H A D | DLL_FAQ.txt | 29 * 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 …]
|
| /netbsd-src/external/gpl3/gcc.old/dist/gcc/doc/ |
| H A D | interface.texi | 12 GCC is normally configured to use the same function calling convention
41 standard system convention is to pass to the subroutine the address of
48 GCC uses the system's standard convention for passing arguments. On
53 incompatibility with code that follows the standard convention. So this
|
| /netbsd-src/external/gpl3/gcc/dist/gcc/doc/ |
| H A D | interface.texi | 12 GCC is normally configured to use the same function calling convention
41 standard system convention is to pass to the subroutine the address of
48 GCC uses the system's standard convention for passing arguments. On
53 incompatibility with code that follows the standard convention. So this
|
| /netbsd-src/sys/arch/shark/shark/ |
| H A D | scr.c | 458 int convention; /* ie direct or inverse */ member
1434 sc->convention = CONVENTION_UNKNOWN; in masterSM()
2877 if (sc->convention == CONVENTION_INVERSE || in t0RecvByteSM()
2878 sc->convention == CONVENTION_UNKNOWN) in t0RecvByteSM()
2891 ASSERT(sc->convention == CONVENTION_DIRECT); in t0RecvByteSM()
2905 if (sc->convention == CONVENTION_UNKNOWN && /* in TS byte */ in t0RecvByteSM()
2933 if (sc->convention == CONVENTION_INVERSE) in t0RecvByteSM()
2940 else if (sc->convention == CONVENTION_DIRECT) in t0RecvByteSM()
2952 ASSERT(sc->convention == CONVENTION_UNKNOWN); in t0RecvByteSM()
2955 sc->convention = CONVENTION_INVERSE; in t0RecvByteSM()
[all …]
|
| /netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/MSP430/ |
| H A D | README.txt | 18 2. Libcalls: multiplication, division, remainder. Note, that calling convention
19 for libcalls is incomptible with calling convention of libcalls of msp430-gcc
|
| /netbsd-src/external/apache2/llvm/dist/llvm/include/llvm/Target/ |
| H A D | TargetCallingConv.td | 74 /// CCIfCC - Match if the current calling convention is 'CC'.
182 /// CCDelegateTo - This action invokes the specified sub-calling-convention. It
188 /// CallingConv - An instance of this is used to define each calling convention
193 /// If true, this calling convention will be emitted as externally visible in
207 /// convention. The order of registers is used by PrologEpilogInsertion when
|
| /netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/AMDGPU/ |
| H A D | AMDGPUCallingConv.td | 18 // Calling convention for SI
175 // Just to get the regmask, not for calling convention purposes.
187 // Just to get the regmask, not for calling convention purposes.
202 // Calling convention for leaf functions
215 // Calling convention for leaf functions
|
| /netbsd-src/external/gpl3/gdb/dist/gnulib/import/m4/ |
| H A D | inet_ntop.m4 | 21 dnl <ws2tcpip.h>, and it uses stdcall calling convention, not cdecl
27 dnl It needs to be overridden, because the stdcall calling convention
|
| /netbsd-src/external/gpl3/gcc.old/dist/libphobos/libdruntime/ |
| H A D | __entrypoint.di | 27 It always has `_Dmain` symbol name and uses C calling convention.
29 As we need to deal with actual calling convention we have to mark it
|
| /netbsd-src/external/lgpl3/gmp/dist/mpn/sparc64/ultrasparct3/ |
| H A D | missing.m4 | 63 dnl Calls __gmpn_umulh using a non-standard calling convention
78 dnl Calls __gmpn_lzcnt using a non-standard calling convention
|
| /netbsd-src/external/bsd/nvi/dist/catalog/ |
| H A D | README | 37 to reorder the arguments or to not display all of them. The convention
38 nvi uses is the System V printf(3) convention, i.e. "%[0-9]*$" is the name
45 If the system supports this convention in its library printf routines
73 message itself. All base files are named using the convention
|
| /netbsd-src/external/apache2/llvm/dist/llvm/docs/ |
| H A D | StackMaps.rst | 33 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.
236 map because they are already fixed by the calling convention. The
239 convention has been introduced for use with stack maps, anyregcc,
259 in $rdi, and a return value in $rax per native calling convention:
282 sequence does not need arguments fixed to specific calling convention
283 registers, then the ``anyregcc`` convention may be used:
389 patchpoint intrinsic is used with a calling convention that by default
|
| /netbsd-src/external/gpl3/binutils/dist/zlib/contrib/vstudio/ |
| H A D | readme.txt | 58 It uses the WINAPI calling convention for the exported functions, and
66 is exporting the functions using the CDECL convention. See the file
|
| /netbsd-src/external/gpl3/binutils.old/dist/zlib/contrib/vstudio/ |
| H A D | readme.txt | 58 It uses the WINAPI calling convention for the exported functions, and
66 is exporting the functions using the CDECL convention. See the file
|
| /netbsd-src/external/gpl3/gdb/dist/zlib/contrib/vstudio/ |
| H A D | readme.txt | 58 It uses the WINAPI calling convention for the exported functions, and
66 is exporting the functions using the CDECL convention. See the file
|
| /netbsd-src/crypto/external/bsd/heimdal/dist/cf/ |
| H A D | krb-sys-aix.m4 | 4 dnl AIX have a very different syscall convention
|