summaryrefslogtreecommitdiffstats
path: root/Modules/CMakeTestCCompiler.cmake
diff options
context:
space:
mode:
authorKWSys Robot <kwrobot@kitware.com>2011-12-13 05:05:03 (GMT)
committerKWSys Robot <kwrobot@kitware.com>2011-12-13 05:05:03 (GMT)
commit3c101429a4e563f4c711cae84317806284784eb6 (patch)
tree88777a399c5b925d99d64744fa36d890c8ba5604 /Modules/CMakeTestCCompiler.cmake
parent99771d55beee37d8e4a1cff19570c2847ce221cd (diff)
downloadCMake-3c101429a4e563f4c711cae84317806284784eb6.zip
CMake-3c101429a4e563f4c711cae84317806284784eb6.tar.gz
CMake-3c101429a4e563f4c711cae84317806284784eb6.tar.bz2
KWSys Nightly Date Stamp
Diffstat (limited to 'Modules/CMakeTestCCompiler.cmake')
0 files changed, 0 insertions, 0 deletions
generated by cgit v0.12 at 2025-03-07 14:02:59 (GMT)
Error message for partially initialized module. ↵Serhiy Storchaka2018-10-301-2/+39 | | | | (GH-6398) * bpo-33234 Improve list() pre-sizing for inputs with known lengths (GH-9846)Pablo Galindo2018-10-281-0/+40 | | | | | | | | | | | | The list() constructor isn't taking full advantage of known input lengths or length hints. This commit makes the constructor pre-size and not over-allocate when the input size is known (the input collection implements __len__). One on the main advantages is that this provides 12% difference in memory savings due to the difference between overallocating and allocating exactly the input size. For efficiency purposes and to avoid a performance regression for small generators and collections, the size of the input object is calculated using __len__ and not __length_hint__, as the later is considerably slower. * bpo-35064 prefix smelly symbols that appear with COUNT_ALLOCS with _Py_ ↵Pablo Galindo2018-10-284-23/+23 | | | | | | | (GH-10152) Configuring python with ./configure --with-pydebug CFLAGS="-D COUNT_ALLOCS -O0" makes "make smelly" fail as some symbols were being exported without the "Py_" or "_Py" prefixes. * bpo-34751: improved hash function for tuples (GH-9471)jdemeyer2018-10-281-25/+46 | * bpo-9263: _PyXXX_CheckConsistency() use _PyObject_ASSERT() (GH-10108)Victor Stinner2018-10-263-52/+64 | | | | | | | | | | Use _PyObject_ASSERT() in: * _PyDict_CheckConsistency() * _PyType_CheckConsistency() * _PyUnicode_CheckConsistency() _PyObject_ASSERT() dumps the faulty object if the assertion fails to help debugging. * bpo-9263: Use _PyObject_ASSERT() in typeobject.c (GH-10111)Victor Stinner2018-10-261-10/+13 | | | | Replace assert() with _PyObject_ASSERT() in Objects/typeobject.c to dump the faulty object on assertion failure to ease debugging. * bpo-9263: Use _PyObject_ASSERT() in object.c (GH-10110)Victor Stinner2018-10-261-18/+22 | | | | Replace assert() with _PyObject_ASSERT() in Objects/object.c to dump the faulty object on assertion failure to ease debugging. * bpo-35059: Convert PyObject_INIT() to function (GH-10077)Victor Stinner2018-10-26