Home
last modified time | relevance | path

Searched refs:STDCALL (Results 1 – 6 of 6) sorted by relevance

/external/clang/test/PCH/
Dsingle-token-macro.c21 #define STDCALL __stdcall macro
23 void STDCALL Foo(void);
27 void STDCALL Foo(void) in Foo()
/external/v8/src/third_party/vtune/
Dittnotify_config.h126 #ifndef STDCALL
128 # define STDCALL __stdcall macro
131 # define STDCALL /* not supported on x86_64 platform */ macro
133 # define STDCALL __attribute__ ((stdcall)) macro
/external/llvm/lib/ExecutionEngine/IntelJITEvents/
Dittnotify_config.h87 #ifndef STDCALL
89 # define STDCALL __stdcall macro
92 # define STDCALL /* not supported on x86_64 platform */ macro
94 # define STDCALL __attribute__ ((stdcall)) macro
/external/vulkan-validation-layers/windowsRuntimeInstaller/
DNSIS_Security.patch14 @@ -29,7 +29,7 @@ defenv['STDCALL'] = '__stdcall'
33 defenv.Append(CPPDEFINES = [('NSISCALL', '$STDCALL')])
/external/syslinux/gpxe/src/crypto/axtls/
Dos_port.h17 #define STDCALL macro
/external/zlib/src/win32/
DDLL_FAQ.txt135 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