Home
last modified time | relevance | path

Searched refs:CDECL (Results 1 – 23 of 23) sorted by relevance

/third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/ExecutionEngine/IntelJITEvents/
Djitprofiling.h223 #ifndef CDECL
225 # define CDECL __cdecl macro
228 # define CDECL /* not actual on x86_64 platform */
230 # define CDECL __attribute__ ((cdecl))
235 #define JITAPI CDECL
Dittnotify_config.h74 #ifndef CDECL
76 # define CDECL __cdecl macro
79 # define CDECL /* not actual on x86_64 platform */ macro
81 # define CDECL __attribute__ ((cdecl)) macro
98 #define ITTAPI CDECL
99 #define LIBITTAPI CDECL
102 #define ITTAPI_CALL CDECL
103 #define LIBITTAPI_CALL CDECL
/third_party/cef/include/base/
Dcef_compiler_specific.h254 #if !defined(CDECL)
256 #define CDECL __cdecl macro
258 #define CDECL macro
/third_party/boost/boost/function_types/config/
Dcc_names.hpp14 (( CDECL , cdecl_cc , BOOST_PP_IDENTITY(__cdecl ) ))\
/third_party/zlib/win32/
DDLL_FAQ.txt29 * The calling convention of functions is "C" (CDECL).
134 6. I see that the ZLIB1.DLL functions use the "C" (CDECL) calling
139 (For readability, we use CDECL to refer to the convention
146 Win32), but the standard C functions use CDECL. If a user
160 faster than CDECL, and it works with variable-argument
161 functions, just like CDECL. It is unfortunate that, in spite
168 The remaining fact is that CDECL is the default convention.
/third_party/boost/tools/boost_install/test/iostreams/zlib-1.2.11/win32/
DDLL_FAQ.txt29 * The calling convention of functions is "C" (CDECL).
134 6. I see that the ZLIB1.DLL functions use the "C" (CDECL) calling
139 (For readability, we use CDECL to refer to the convention
146 Win32), but the standard C functions use CDECL. If a user
160 faster than CDECL, and it works with variable-argument
161 functions, just like CDECL. It is unfortunate that, in spite
168 The remaining fact is that CDECL is the default convention.
/third_party/boost/tools/boost_install/test/iostreams/zlib-1.2.11/contrib/vstudio/
Dreadme.txt66 is exporting the functions using the CDECL convention. See the file
/third_party/boost/libs/beast/test/extern/zlib-1.2.11/contrib/vstudio/
Dreadme.txt66 is exporting the functions using the CDECL convention. See the file
/third_party/zlib/contrib/vstudio/
Dreadme.txt66 is exporting the functions using the CDECL convention. See the file
/third_party/libwebsockets/win32port/zlib/
Dzconf.h302 # define ZEXPORTVA FAR CDECL
/third_party/zlib/
Dzconf.h359 # define ZEXPORTVA FAR CDECL
Dzconf.h.in359 # define ZEXPORTVA FAR CDECL
Dzconf.h.cmakein361 # define ZEXPORTVA FAR CDECL
/third_party/skia/third_party/externals/zlib/
Dzconf.h371 # define ZEXPORTVA FAR CDECL
/third_party/boost/libs/beast/test/extern/zlib-1.2.11/
Dzconf.h359 # define ZEXPORTVA FAR CDECL
Dzconf.h.cmakein361 # define ZEXPORTVA FAR CDECL
Dzconf.h.in359 # define ZEXPORTVA FAR CDECL
/third_party/node/deps/zlib/
Dzconf.h371 # define ZEXPORTVA FAR CDECL
/third_party/flutter/skia/third_party/externals/zlib/
Dzconf.h362 # define ZEXPORTVA FAR CDECL
/third_party/boost/tools/boost_install/test/iostreams/zlib-1.2.11/
Dzconf.h359 # define ZEXPORTVA FAR CDECL
Dzconf.h.cmakein361 # define ZEXPORTVA FAR CDECL
Dzconf.h.in359 # define ZEXPORTVA FAR CDECL
/third_party/boost/libs/function_types/doc/
Dfunction_types.qbk923 (( CDECL , cdecl_cc , BOOST_PP_IDENTITY(__cdecl ) ))\