Searched refs:STDCALL (Results 1 – 10 of 10) sorted by relevance
| /external/clang/test/PCH/ |
| D | single-token-macro.c | 21 #define STDCALL __stdcall macro
23 void STDCALL Foo(void);
27 void STDCALL Foo(void) in Foo()
|
| /external/llvm-project/clang/test/PCH/ |
| D | single-token-macro.c | 21 #define STDCALL __stdcall macro
23 void STDCALL Foo(void);
27 void STDCALL Foo(void) in Foo()
|
| /external/llvm/lib/ExecutionEngine/IntelJITEvents/ |
| D | ittnotify_config.h | 87 #ifndef STDCALL
89 # define STDCALL __stdcall macro
92 # define STDCALL /* not supported on x86_64 platform */ macro
94 # define STDCALL __attribute__ ((stdcall)) macro
|
| /external/swiftshader/third_party/llvm-10.0/llvm/lib/ExecutionEngine/IntelJITEvents/ |
| D | ittnotify_config.h | 86 #ifndef STDCALL
88 # define STDCALL __stdcall macro
91 # define STDCALL /* not supported on x86_64 platform */ macro
93 # define STDCALL __attribute__ ((stdcall)) macro
|
| /external/llvm-project/llvm/lib/ExecutionEngine/IntelJITEvents/ |
| D | ittnotify_config.h | 86 #ifndef STDCALL
88 # define STDCALL __stdcall macro
91 # define STDCALL /* not supported on x86_64 platform */ macro
93 # define STDCALL __attribute__ ((stdcall)) macro
|
| /external/llvm-project/openmp/runtime/src/thirdparty/ittnotify/ |
| D | ittnotify_config.h | 96 #ifndef STDCALL
98 # define STDCALL __stdcall macro
101 # define STDCALL __attribute__ ((stdcall)) macro
103 # define STDCALL /* supported only on x86 platform */ macro
|
| D | ittnotify.h | 162 #ifndef STDCALL
164 # define STDCALL __stdcall macro
167 # define STDCALL __attribute__ ((stdcall)) macro
169 # define STDCALL /* supported only on x86 platform */ macro
|
| /external/rust/crates/libz-sys/src/zlib/win32/ |
| D | DLL_FAQ.txt | 135 convention. Why not use the STDCALL convention?
136 STDCALL is the standard convention in Win32, and I need it in
140 triggered by the "__cdecl" keyword, STDCALL to refer to
145 indeed the WINAPI convention (which translates to STDCALL in
154 functions STDCALL-able.
159 Technically, STDCALL is not bad; in fact, it is slightly
162 of using STDCALL in the Windows API, it is not the default
179 Basic require STDCALL, while Borland Delphi prefers, although
196 (STDCALL) convention. The name of this DLL must be different
|
| /external/rust/crates/libz-sys/src/zlib-ng/win32/ |
| D | DLL_FAQ.txt | 135 convention. Why not use the STDCALL convention?
136 STDCALL is the standard convention in Win32, and I need it in
140 triggered by the "__cdecl" keyword, STDCALL to refer to
145 indeed the WINAPI convention (which translates to STDCALL in
154 functions STDCALL-able.
159 Technically, STDCALL is not bad; in fact, it is slightly
162 of using STDCALL in the Windows API, it is not the default
179 Basic require STDCALL, while Borland Delphi prefers, although
196 (STDCALL) convention. The name of this DLL must be different
|
| /external/llvm-project/openmp/runtime/src/thirdparty/ittnotify/legacy/ |
| D | ittnotify.h | 101 #ifndef STDCALL
103 # define STDCALL __stdcall macro
106 # define STDCALL __attribute__ ((stdcall)) macro
108 # define STDCALL /* supported only on x86 platform */ macro
|