Hi, I have installed python3-pygame V2.5.2.1 from the Fedora repositories, and when I import it into python3 3.12 (installed from the Fedora repositories) I get the following message:
<frozen importlib._bootstrap>:488: RuntimeWarning: Your system is avx2 capable but pygame was not built with support for it. The performance of some of your blits could be adversely affected. Consider enabling compile time detection with environment variables like PYGAME_DETECT_AVX2=1 if you are compiling without cross compilation. How do I fix this or is the message irrelevant?
regards, Steve
On 3/19/24 15:25, Stephen Morris wrote:
I have installed python3-pygame V2.5.2.1 from the Fedora repositories, and when I import it into python3 3.12 (installed from the Fedora repositories) I get the following message:
<frozen importlib._bootstrap>:488: RuntimeWarning: Your system is avx2 capable but pygame was not built with support for it. The performance of some of your blits could be adversely affected. Consider enabling compile time detection with environment variables like PYGAME_DETECT_AVX2=1 if you are compiling without cross compilation. How do I fix this or is the message irrelevant?
It's not going to break anything, but I suggest filing a bug on the package with that suggestion.
On Tue, Mar 19, 2024 at 4:32 PM Samuel Sieb samuel@sieb.net wrote:
On 3/19/24 15:25, Stephen Morris wrote:
I have installed python3-pygame V2.5.2.1 from the Fedorarepositories, and when I import it into python3 3.12 (installed from the Fedora repositories) I get the following message:
<frozen importlib._bootstrap>:488: RuntimeWarning: Your system is avx2 capable but pygame was not built with support for it. The performance of some of your blits could be adversely affected. Consider enabling compile time detection with environment variables like PYGAME_DETECT_AVX2=1 if you are compiling without cross compilation. How do I fix this or is the message irrelevant?
It's not going to break anything, but I suggest filing a bug on the package with that suggestion.
Compile-time detection of AVX2 is no good. Fedora supports pre-AVX2 CPUs. If upstream can be convinced to do runtime detection of AVX2, that would be great.
On 3/19/24 16:24, Jerry James wrote:
On Tue, Mar 19, 2024 at 4:32 PM Samuel Sieb samuel@sieb.net wrote:
On 3/19/24 15:25, Stephen Morris wrote:
I have installed python3-pygame V2.5.2.1 from the Fedorarepositories, and when I import it into python3 3.12 (installed from the Fedora repositories) I get the following message:
<frozen importlib._bootstrap>:488: RuntimeWarning: Your system is avx2 capable but pygame was not built with support for it. The performance of some of your blits could be adversely affected. Consider enabling compile time detection with environment variables like PYGAME_DETECT_AVX2=1 if you are compiling without cross compilation. How do I fix this or is the message irrelevant?
It's not going to break anything, but I suggest filing a bug on the package with that suggestion.
Compile-time detection of AVX2 is no good. Fedora supports pre-AVX2 CPUs. If upstream can be convinced to do runtime detection of AVX2, that would be great.
Right, I misread that. Never mind filing that bug. :-)
On 20/3/24 10:24, Jerry James wrote:
On Tue, Mar 19, 2024 at 4:32 PM Samuel Sieb samuel@sieb.net wrote:
On 3/19/24 15:25, Stephen Morris wrote:
I have installed python3-pygame V2.5.2.1 from the Fedorarepositories, and when I import it into python3 3.12 (installed from the Fedora repositories) I get the following message:
<frozen importlib._bootstrap>:488: RuntimeWarning: Your system is avx2 capable but pygame was not built with support for it. The performance of some of your blits could be adversely affected. Consider enabling compile time detection with environment variables like PYGAME_DETECT_AVX2=1 if you are compiling without cross compilation. How do I fix this or is the message irrelevant?
It's not going to break anything, but I suggest filing a bug on the package with that suggestion.
Compile-time detection of AVX2 is no good. Fedora supports pre-AVX2 CPUs. If upstream can be convinced to do runtime detection of AVX2, that would be great.
Thankyou. Just a couple of silly questions: AVX cpu's, both Intel and AMD, have been around since 2008, and this is 2024, why does Fedora not have support for the AVXx instruction sets? Given that the AVX instruction set is heavily into Integer Maths functionality why does the python import of the math module not produce the message that an import of the pygame module does (Is pygame producing because of the instruction set Vector interactions?).
regards, Steve
On 20 Mar 2024, at 22:19, Stephen Morris samorris@netspace.net.au wrote:
Just a couple of silly questions: AVX cpu's, both Intel and AMD, have been around since 2008, and this is 2024, why does Fedora not have support for the AVXx instruction sets?
Not all recent CPUs have AVX, only some CPUs I believe. Therefore the preference for detect at runtime.
Barry
On 22/3/24 00:18, Barry wrote:
On 20 Mar 2024, at 22:19, Stephen Morris samorris@netspace.net.au wrote:
Just a couple of silly questions: AVX cpu's, both Intel and AMD, have been around since 2008, and this is 2024, why does Fedora not have support for the AVXx instruction sets?
Not all recent CPUs have AVX, only some CPUs I believe. Therefore the preference for detect at runtime.
I can understand the runtime detection, but why is pygame, presumably with its support for vectors, not compiled to use AVX if available. The math module doesn't produce the message, even though AVX can be used with integer manipulations, does that mean it has been compiled with AVX support or is it not checking for support? With, in this case, the pygame module having been installed from the Fedora repositories and producing this issue, does that mean I shouldn't install the modules from the Fedora repositories, I should use pip3 to install the modules as they may be compiled with AVX support? The message I got indicated that my cpu supports AVX2, how do I determine if it supports AVX512?
regards, Steve
Barry
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 3/21/24 14:45, Stephen Morris wrote:
On 22/3/24 00:18, Barry wrote:
On 20 Mar 2024, at 22:19, Stephen Morris samorris@netspace.net.au wrote:
Just a couple of silly questions: AVX cpu's, both Intel and AMD, have been around since 2008, and this is 2024, why does Fedora not have support for the AVXx instruction sets?
Not all recent CPUs have AVX, only some CPUs I believe. Therefore the preference for detect at runtime.
I can understand the runtime detection, but why is pygame, presumably with its support for vectors, not compiled to use AVX if available. The math module doesn't produce the message, even though AVX can be used with integer manipulations, does that mean it has been compiled with AVX support or is it not checking for support? With, in this case, the pygame module having been installed from the Fedora repositories and producing this issue, does that mean I shouldn't install the modules from the Fedora repositories, I should use pip3 to install the modules as they may be compiled with AVX support? The message I got indicated that my cpu supports AVX2, how do I determine if it supports AVX512?
The message is about AVX2, not AVX. The computer I'm currently using is an Intel Xeon from 2019 or maybe a bit earlier. It has AVX, but not any of the higher ones.
You can look in /proc/cpuinfo to see the flags, or install "cpuid" to get very detailed information.
On 22/3/24 09:07, Samuel Sieb wrote:
On 3/21/24 14:45, Stephen Morris wrote:
On 22/3/24 00:18, Barry wrote:
On 20 Mar 2024, at 22:19, Stephen Morris samorris@netspace.net.au wrote:
Just a couple of silly questions: AVX cpu's, both Intel and AMD, have been around since 2008, and this is 2024, why does Fedora not have support for the AVXx instruction sets?
Not all recent CPUs have AVX, only some CPUs I believe. Therefore the preference for detect at runtime.
I can understand the runtime detection, but why is pygame, presumably with its support for vectors, not compiled to use AVX if available. The math module doesn't produce the message, even though AVX can be used with integer manipulations, does that mean it has been compiled with AVX support or is it not checking for support? With, in this case, the pygame module having been installed from the Fedora repositories and producing this issue, does that mean I shouldn't install the modules from the Fedora repositories, I should use pip3 to install the modules as they may be compiled with AVX support? The message I got indicated that my cpu supports AVX2, how do I determine if it supports AVX512?
The message is about AVX2, not AVX. The computer I'm currently using is an Intel Xeon from 2019 or maybe a bit earlier. It has AVX, but not any of the higher ones.
You can look in /proc/cpuinfo to see the flags, or install "cpuid" to get very detailed information.
Thanks Samuel. I don't actually need that level of support, I was just curious. Until I got the message I hadn't thought about anything related to AVX. The only reason I got the message was I'm following lessons in a Python book to refresh my python knowledge for future use at work, and the book was using pygame as an example of how to import modules. I'm running an AMD Ryzen 9 5950X 16-Core which I installed 18 months or so ago.
regards, Steve
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Thu, Mar 21, 2024 at 6:07 PM Samuel Sieb samuel@sieb.net wrote:
On 3/21/24 14:45, Stephen Morris wrote:
On 22/3/24 00:18, Barry wrote:
On 20 Mar 2024, at 22:19, Stephen Morris samorris@netspace.net.au wrote:
Just a couple of silly questions: AVX cpu's, both Intel and AMD, have been around since 2008, and this is 2024, why does Fedora not have support for the AVXx instruction sets?
Not all recent CPUs have AVX, only some CPUs I believe. Therefore the preference for detect at runtime.
I can understand the runtime detection, but why is pygame, presumably with its support for vectors, not compiled to use AVX if available. The math module doesn't produce the message, even though AVX can be used with integer manipulations, does that mean it has been compiled with AVX support or is it not checking for support? With, in this case, the pygame module having been installed from the Fedora repositories and producing this issue, does that mean I shouldn't install the modules from the Fedora repositories, I should use pip3 to install the modules as they may be compiled with AVX support? The message I got indicated that my cpu supports AVX2, how do I determine if it supports AVX512?
The message is about AVX2, not AVX. The computer I'm currently using is an Intel Xeon from 2019 or maybe a bit earlier. It has AVX, but not any of the higher ones.
It is common to see manufacturers of low-end tablets and pc's buying cpu's from Intel that only have SSE2-SSE4.1+AES+RDRAND enabled. I encounter them regularly in low-end netbooks. The cpu's probably have higher ISAs, they just are not enabled.
Intel will also de-clock or slow down the cpu for the price point. I was talking to David Johnson, who designed Intel's RDRAND circuit. He told me intel can tune about 100 different parameters to vary cpu features and speeds for a particular price point.
You can look in /proc/cpuinfo to see the flags, or install "cpuid" to get very detailed information.
Jeff
-
Barry -
Jeffrey Walton -
Jerry James -
Samuel Sieb -
Stephen Morris