Displaying 3 results from an estimated 3 matches for "detectcpus".
Did you mean:
detect_cpu
2016 Feb 23
2
Can lit be upgraded to assume Python 2.7?
In the root llvm/CMakeLists.txt we have:
if( ${PYTHON_VERSION_STRING} VERSION_LESS 2.7 )
message(FATAL_ERROR "Python 2.7 or newer is required")
endif()
But lit seems to still be stuck in a Python 2.5 world. For example,
detectCPUs is redundant now that we have multiprocessing.cpu_count()
(multiprocessing requires >=2.6). And there are a bunch of other Python 2.5
workarounds floating around inside lit. I'm actually not sure if there are
2.6 workarounds.
Anyway, does anybody know if somehow, despite the CMake check, li...
2016 Feb 24
3
Can lit be upgraded to assume Python 2.7?
...lists.llvm.org>> wrote:
> In the root llvm/CMakeLists.txt we have:
>
> if( ${PYTHON_VERSION_STRING} VERSION_LESS 2.7 )
> message(FATAL_ERROR "Python 2.7 or newer is required")
> endif()
>
> But lit seems to still be stuck in a Python 2.5 world. For example, detectCPUs is redundant now that we have multiprocessing.cpu_count() (multiprocessing requires >=2.6). And there are a bunch of other Python 2.5 workarounds floating around inside lit. I'm actually not sure if there are 2.6 workarounds.
>
> Anyway, does anybody know if somehow, despite the CMake...
2016 Feb 24
0
Can lit be upgraded to assume Python 2.7?
...> In the root llvm/CMakeLists.txt we have:
>>
>> if( ${PYTHON_VERSION_STRING} VERSION_LESS 2.7 )
>> message(FATAL_ERROR "Python 2.7 or newer is required")
>> endif()
>>
>> But lit seems to still be stuck in a Python 2.5 world. For example,
>> detectCPUs is redundant now that we have multiprocessing.cpu_count()
>> (multiprocessing requires >=2.6). And there are a bunch of other Python 2.5
>> workarounds floating around inside lit. I'm actually not sure if there are
>> 2.6 workarounds.
>>
>> Anyway, does anybody...