Buckets:
| /* Defines to build Python and its standard library: | |
| * | |
| * - Py_BUILD_CORE: Build Python core. Give access to Python internals, but | |
| * should not be used by third-party modules. | |
| * - Py_BUILD_CORE_BUILTIN: Build a Python stdlib module as a built-in module. | |
| * - Py_BUILD_CORE_MODULE: Build a Python stdlib module as a dynamic library. | |
| * | |
| * Py_BUILD_CORE_BUILTIN and Py_BUILD_CORE_MODULE imply Py_BUILD_CORE. | |
| * | |
| * On Windows, Py_BUILD_CORE_MODULE exports "PyInit_xxx" symbol, whereas | |
| * Py_BUILD_CORE_BUILTIN does not. | |
| */ | |
| /************************************************************************** | |
| Symbols and macros to supply platform-independent interfaces to basic | |
| C language & library operations whose spellings vary across platforms. | |
| Please try to make documentation here as clear as possible: by definition, | |
| the stuff here is trying to illuminate C's darkest corners. | |
| Config #defines referenced here: | |
| SIGNED_RIGHT_SHIFT_ZERO_FILLS | |
| Meaning: To be defined iff i>>j does not extend the sign bit when i is a | |
| signed integral type and i < 0. | |
| Used in: Py_ARITHMETIC_RIGHT_SHIFT | |
| Py_DEBUG | |
| Meaning: Extra checks compiled in for debug mode. | |
| Used in: Py_SAFE_DOWNCAST | |
| **************************************************************************/ | |
| /* typedefs for some C9X-defined synonyms for integral types. | |
| * | |
| * The names in Python are exactly the same as the C9X names, except with a | |
| * Py_ prefix. Until C9X is universally implemented, this is the only way | |
| * to ensure that Python gets reliable names that don't conflict with names | |
| * in non-Python code that are playing their own tricks to define the C9X | |
| * names. | |
| * | |
| * NOTE: don't go nuts here! Python has no use for *most* of the C9X | |
| * integral synonyms. Only define the ones we actually need. | |
| */ | |
| /* long long is required. Ensure HAVE_LONG_LONG is defined for compatibility. */ | |
| /* If LLONG_MAX is defined in limits.h, use that. */ | |
| /* Signed variants of the above */ | |
| /* If PYLONG_BITS_IN_DIGIT is not defined then we'll use 30-bit digits if all | |
| the necessary integer types are available, and we're on a 64-bit platform | |
| (as determined by SIZEOF_VOID_P); otherwise we use 15-bit digits. */ | |
| /* uintptr_t is the C9X name for an unsigned integral type such that a | |
| * legitimate void* can be cast to uintptr_t and then back to void* again | |
| * without loss of information. Similarly for intptr_t, wrt a signed | |
| * integral type. | |
| */ | |
| typedef uintptr_t Py_uintptr_t; | |
| typedef intptr_t Py_intptr_t; | |
| /* Py_ssize_t is a signed integral type such that sizeof(Py_ssize_t) == | |
| * sizeof(size_t). C99 doesn't define such a thing directly (size_t is an | |
| * unsigned integral type). See PEP 353 for details. | |
| */ | |
| typedef ssize_t Py_ssize_t; | |
| typedef Py_intptr_t Py_ssize_t; | |
| /* Py_hash_t is the same size as a pointer. */ | |
| typedef Py_ssize_t Py_hash_t; | |
| /* Py_uhash_t is the unsigned equivalent needed to calculate numeric hash. */ | |
| typedef size_t Py_uhash_t; | |
| /* Only used for compatibility with code that may not be PY_SSIZE_T_CLEAN. */ | |
| typedef Py_ssize_t Py_ssize_clean_t; | |
| typedef int Py_ssize_clean_t; | |
| /* Largest possible value of size_t. */ | |
| /* Largest positive value of type Py_ssize_t. */ | |
| /* Smallest negative value of type Py_ssize_t. */ | |
| /* Macro kept for backward compatibility: use "z" in new code. | |
| * | |
| * PY_FORMAT_SIZE_T is a platform-specific modifier for use in a printf | |
| * format to convert an argument with the width of a size_t or Py_ssize_t. | |
| * C99 introduced "z" for this purpose, but old MSVCs had not supported it. | |
| * Since MSVC supports "z" since (at least) 2015, we can just use "z" | |
| * for new code. | |
| * | |
| * These "high level" Python format functions interpret "z" correctly on | |
| * all platforms (Python interprets the format string itself, and does whatever | |
| * the platform C requires to convert a size_t/Py_ssize_t argument): | |
| * | |
| * PyBytes_FromFormat | |
| * PyErr_Format | |
| * PyBytes_FromFormatV | |
| * PyUnicode_FromFormatV | |
| * | |
| * Lower-level uses require that you interpolate the correct format modifier | |
| * yourself (e.g., calling printf, fprintf, sprintf, PyOS_snprintf); for | |
| * example, | |
| * | |
| * Py_ssize_t index; | |
| * fprintf(stderr, "index %" PY_FORMAT_SIZE_T "d sucks\n", index); | |
| * | |
| * That will expand to %zd or to something else correct for a Py_ssize_t on | |
| * the platform. | |
| */ | |
| /* Py_LOCAL can be used instead of static to get the fastest possible calling | |
| * convention for functions that are local to a given module. | |
| * | |
| * Py_LOCAL_INLINE does the same thing, and also explicitly requests inlining, | |
| * for platforms that support that. | |
| * | |
| * If PY_LOCAL_AGGRESSIVE is defined before python.h is included, more | |
| * "aggressive" inlining/optimization is enabled for the entire module. This | |
| * may lead to code bloat, and may slow things down for those reasons. It may | |
| * also lead to errors, if the code relies on pointer aliasing. Use with | |
| * care. | |
| * | |
| * NOTE: You can only use this for functions that are entirely local to a | |
| * module; functions that are exported via method tables, callbacks, etc, | |
| * should keep using static. | |
| */ | |
| /* enable more aggressive optimization for MSVC */ | |
| /* active in both release and debug builds - see bpo-43271 */ | |
| /* ignore warnings if the compiler decides not to inline a function */ | |
| /* fastest possible local call under MSVC */ | |
| /* Py_MEMCPY is kept for backwards compatibility, | |
| * see https://bugs.python.org/issue28126 */ | |
| /******************************************** | |
| * WRAPPER FOR <time.h> and/or <sys/time.h> * | |
| ********************************************/ | |
| /****************************** | |
| * WRAPPER FOR <sys/select.h> * | |
| ******************************/ | |
| /* NB caller must include <sys/types.h> */ | |
| /******************************* | |
| * stat() and fstat() fiddling * | |
| *******************************/ | |
| /* VisualAge C/C++ Failed to Define MountType Field in sys/stat.h */ | |
| /* Windows doesn't define S_IFLNK but posixmodule.c maps | |
| * IO_REPARSE_TAG_SYMLINK to S_IFLNK */ | |
| /* Move this down here since some C++ #include's don't like to be included | |
| inside an extern "C" */ | |
| extern "C" { | |
| /* Py_ARITHMETIC_RIGHT_SHIFT | |
| * C doesn't define whether a right-shift of a signed integer sign-extends | |
| * or zero-fills. Here a macro to force sign extension: | |
| * Py_ARITHMETIC_RIGHT_SHIFT(TYPE, I, J) | |
| * Return I >> J, forcing sign extension. Arithmetically, return the | |
| * floor of I/2**J. | |
| * Requirements: | |
| * I should have signed integer type. In the terminology of C99, this can | |
| * be either one of the five standard signed integer types (signed char, | |
| * short, int, long, long long) or an extended signed integer type. | |
| * J is an integer >= 0 and strictly less than the number of bits in the | |
| * type of I (because C doesn't define what happens for J outside that | |
| * range either). | |
| * TYPE used to specify the type of I, but is now ignored. It's been left | |
| * in for backwards compatibility with versions <= 2.6 or 3.0. | |
| * Caution: | |
| * I may be evaluated more than once. | |
| */ | |
| /* Py_FORCE_EXPANSION(X) | |
| * "Simply" returns its argument. However, macro expansions within the | |
| * argument are evaluated. This unfortunate trickery is needed to get | |
| * token-pasting to work as desired in some cases. | |
| */ | |
| /* Py_SAFE_DOWNCAST(VALUE, WIDE, NARROW) | |
| * Cast VALUE to type NARROW from type WIDE. In Py_DEBUG mode, this | |
| * assert-fails if any information is lost. | |
| * Caution: | |
| * VALUE may be evaluated more than once. | |
| */ | |
| /* Py_SET_ERRNO_ON_MATH_ERROR(x) | |
| * If a libm function did not set errno, but it looks like the result | |
| * overflowed or not-a-number, set errno to ERANGE or EDOM. Set errno | |
| * to 0 before calling a libm function, and invoke this macro after, | |
| * passing the function result. | |
| * Caution: | |
| * This isn't reliable. See Py_OVERFLOWED comments. | |
| * X is evaluated more than once. | |
| */ | |
| /* Py_SET_ERANGE_IF_OVERFLOW(x) | |
| * An alias of Py_SET_ERRNO_ON_MATH_ERROR for backward-compatibility. | |
| */ | |
| /* Py_ADJUST_ERANGE1(x) | |
| * Py_ADJUST_ERANGE2(x, y) | |
| * Set errno to 0 before calling a libm function, and invoke one of these | |
| * macros after, passing the function result(s) (Py_ADJUST_ERANGE2 is useful | |
| * for functions returning complex results). This makes two kinds of | |
| * adjustments to errno: (A) If it looks like the platform libm set | |
| * errno=ERANGE due to underflow, clear errno. (B) If it looks like the | |
| * platform libm overflowed but didn't set errno, force errno to ERANGE. In | |
| * effect, we're trying to force a useful implementation of C89 errno | |
| * behavior. | |
| * Caution: | |
| * This isn't reliable. See Py_OVERFLOWED comments. | |
| * X and Y may be evaluated more than once. | |
| */ | |
| /* The functions _Py_dg_strtod and _Py_dg_dtoa in Python/dtoa.c (which are | |
| * required to support the short float repr introduced in Python 3.1) require | |
| * that the floating-point unit that's being used for arithmetic operations | |
| * on C doubles is set to use 53-bit precision. It also requires that the | |
| * FPU rounding mode is round-half-to-even, but that's less often an issue. | |
| * | |
| * If your FPU isn't already set to 53-bit precision/round-half-to-even, and | |
| * you want to make use of _Py_dg_strtod and _Py_dg_dtoa, then you should | |
| * | |
| * #define HAVE_PY_SET_53BIT_PRECISION 1 | |
| * | |
| * and also give appropriate definitions for the following three macros: | |
| * | |
| * _PY_SET_53BIT_PRECISION_START : store original FPU settings, and | |
| * set FPU to 53-bit precision/round-half-to-even | |
| * _PY_SET_53BIT_PRECISION_END : restore original FPU settings | |
| * _PY_SET_53BIT_PRECISION_HEADER : any variable declarations needed to | |
| * use the two macros above. | |
| * | |
| * The macros are designed to be used within a single C function: see | |
| * Python/pystrtod.c for an example of their use. | |
| */ | |
| /* get and set x87 control word for gcc/x86 */ | |
| /* _Py_get/set_387controlword functions are defined in Python/pymath.c */ | |
| /* get and set x87 control word for VisualStudio/x86 */ | |
| /* We use the __control87_2 function to set only the x87 control word. | |
| The SSE control word is unaffected. */ | |
| /* default definitions are empty */ | |
| /* If we can't guarantee 53-bit precision, don't use the code | |
| in Python/dtoa.c, but fall back to standard code. This | |
| means that repr of a float will be long (17 sig digits). | |
| Realistically, there are two things that could go wrong: | |
| (1) doubles aren't IEEE 754 doubles, or | |
| (2) we're on x86 with the rounding precision set to 64-bits | |
| (extended precision), and we don't know how to change | |
| the rounding precision. | |
| */ | |
| /* double rounding is symptomatic of use of extended precision on x86. If | |
| we're seeing double rounding, and we don't have any mechanism available for | |
| changing the FPU rounding precision, then don't use Python/dtoa.c. */ | |
| /* Py_DEPRECATED(version) | |
| * Declare a variable, type, or function deprecated. | |
| * The macro must be placed before the declaration. | |
| * Usage: | |
| * Py_DEPRECATED(3.3) extern int old_var; | |
| * Py_DEPRECATED(3.4) typedef int T1; | |
| * Py_DEPRECATED(3.8) PyAPI_FUNC(int) Py_OldFunction(void); | |
| */ | |
| /* _Py_HOT_FUNCTION | |
| * The hot attribute on a function is used to inform the compiler that the | |
| * function is a hot spot of the compiled program. The function is optimized | |
| * more aggressively and on many target it is placed into special subsection of | |
| * the text section so all hot functions appears close together improving | |
| * locality. | |
| * | |
| * Usage: | |
| * int _Py_HOT_FUNCTION x(void) { return 3; } | |
| * | |
| * Issue #28618: This attribute must not be abused, otherwise it can have a | |
| * negative effect on performance. Only the functions were Python spend most of | |
| * its time must use it. Use a profiler when running performance benchmark | |
| * suite to find these functions. | |
| */ | |
| /* _Py_NO_INLINE | |
| * Disable inlining on a function. For example, it helps to reduce the C stack | |
| * consumption. | |
| * | |
| * Usage: | |
| * int _Py_NO_INLINE x(void) { return 3; } | |
| */ | |
| /************************************************************************** | |
| Prototypes that are missing from the standard include files on some systems | |
| (and possibly only some versions of such systems.) | |
| Please be conservative with adding new ones, document them and enclose them | |
| in platform-specific #ifdefs. | |
| **************************************************************************/ | |
| /* Unchecked */ | |
| extern int gethostname(char *, int); | |
| extern char * _getpty(int *, int, mode_t, int); | |
| /* On QNX 6, struct termio must be declared by including sys/termio.h | |
| if TCGETA, TCSETA, TCSETAW, or TCSETAF are used. sys/termio.h must | |
| be included before termios.h or it will generate an error. */ | |
| /* On 4.4BSD-descendants, ctype functions serves the whole range of | |
| * wchar_t character set rather than single byte code points only. | |
| * This characteristic can break some operations of string object | |
| * including str.upper() and str.split() on UTF-8 locales. This | |
| * workaround was provided by Tim Robbins of FreeBSD project. | |
| */ | |
| /* The workaround below is unsafe in C++ because | |
| * the <locale> defines these symbols as real functions, | |
| * with a slightly different signature. | |
| * See issue #10910 | |
| */ | |
| /* Declarations for symbol visibility. | |
| PyAPI_FUNC(type): Declares a public Python API function and return type | |
| PyAPI_DATA(type): Declares public Python data and its type | |
| PyMODINIT_FUNC: A Python module init function. If these functions are | |
| inside the Python core, they are private to the core. | |
| If in an extension module, it may be declared with | |
| external linkage depending on the platform. | |
| As a number of platforms support/require "__declspec(dllimport/dllexport)", | |
| we support a HAVE_DECLSPEC_DLL macro to save duplication. | |
| */ | |
| /* | |
| All windows ports, except cygwin, are handled in PC/pyconfig.h. | |
| Cygwin is the only other autoconf platform requiring special | |
| linkage handling and it uses __declspec(). | |
| */ | |
| /* only get special linkage if built as shared or platform is Cygwin */ | |
| /* module init functions inside the core need no external linkage */ | |
| /* except for Cygwin to handle embedding */ | |
| /* Building an extension module, or an embedded situation */ | |
| /* public Python functions and data are imported */ | |
| /* Under Cygwin, auto-import functions to prevent compilation */ | |
| /* failures similar to those described at the bottom of 4.1: */ | |
| /* http://docs.python.org/extending/windows.html#a-cookbook-approach */ | |
| /* module init functions outside the core must be exported */ | |
| /* If no external linkage macros defined by now, create defaults */ | |
| /* limits.h constants that may be missing */ | |
| /* 04-Oct-2000 LONG_BIT is apparently (mis)defined as 64 on some recent | |
| * 32-bit platforms using gcc. We try to catch that here at compile-time | |
| * rather than waiting for integer multiplication to trigger bogus | |
| * overflows. | |
| */ | |
| } | |
| /* | |
| * Hide GCC attributes from compilers that don't support them. | |
| */ | |
| /* | |
| * Specify alignment on compilers that support it. | |
| */ | |
| /* Eliminate end-of-loop code not reached warnings from SunPro C | |
| * when using do{...}while(0) macros | |
| */ | |
| /* | |
| * Convenient macros to deal with endianness of the platform. WORDS_BIGENDIAN is | |
| * detected by configure and defined in pyconfig.h. The code in pyconfig.h | |
| * also takes care of Apple's universal builds. | |
| */ | |
| /* | |
| * Macros to protect CRT calls against instant termination when passed an | |
| * invalid parameter (issue23524). | |
| */ | |
| extern _invalid_parameter_handler _Py_silent_invalid_parameter_handler; | |
| /* The Android langinfo.h header is not used. */ | |
| /* Maximum value of the Windows DWORD type */ | |
| /* This macro used to tell whether Python was built with multithreading | |
| * enabled. Now multithreading is always enabled, but keep the macro | |
| * for compatibility. | |
| */ | |
| /* Check that ALT_SOABI is consistent with Py_TRACE_REFS: | |
| ./configure --with-trace-refs should must be used to define Py_TRACE_REFS */ | |
| // Use UTF-8 as the locale encoding, ignore the LC_CTYPE locale. | |
| // See _Py_GetLocaleEncoding(), PyUnicode_DecodeLocale() | |
| // and PyUnicode_EncodeLocale(). | |
| // Use UTF-8 as the filesystem encoding. | |
| // See PyUnicode_DecodeFSDefaultAndSize(), PyUnicode_EncodeFSDefault(), | |
| // Py_DecodeLocale() and Py_EncodeLocale(). | |
| /* Mark a function which cannot return. Example: | |
| PyAPI_FUNC(void) _Py_NO_RETURN PyThread_exit_thread(void); | |
| XLC support is intentionally omitted due to bpo-40244 */ | |
| // Preprocessor check for a builtin preprocessor function. Always return 0 | |
| // if __has_builtin() macro is not defined. | |
| // | |
| // __has_builtin() is available on clang and GCC 10. | |
Xet Storage Details
- Size:
- 31.7 kB
- Xet hash:
- 447a1e7c494787c96571a2c3660177ec454237af5434a16fb750e609e9d58ffc
·
Xet efficiently stores files, intelligently splitting them into unique chunks and accelerating uploads and downloads. More info.