Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build with PYGAME_DETECT_AVX2=1 #20

Open
1 task done
garymm opened this issue Jan 31, 2024 · 3 comments
Open
1 task done

build with PYGAME_DETECT_AVX2=1 #20

garymm opened this issue Jan 31, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@garymm
Copy link

garymm commented Jan 31, 2024

Solution to issue cannot be found in the documentation.

  • I checked the documentation.

Issue

When running on amd64 I see this warning:
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.

Installed packages

pygame                    2.5.2           py311h7bd3ff0_2    conda-forge

Environment info

active environment : minetest
    active env location : /home/garymm/.conda/envs/minetest
            shell level : 2
       user config file : /home/garymm/.condarc
 populated config files : /opt/conda/.condarc
          conda version : 23.11.0
    conda-build version : not installed
         python version : 3.10.13.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=broadwell
                          __conda=23.11.0=0
                          __cuda=12.2=0
                          __glibc=2.35=0
                          __linux=5.15.0=0
                          __unix=0=0
       base environment : /opt/conda  (read only)
      conda av data dir : /opt/conda/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /opt/conda/pkgs
                          /home/garymm/.conda/pkgs
       envs directories : /home/garymm/.conda/envs
                          /opt/conda/envs
               platform : linux-64
             user-agent : conda/23.11.0 requests/2.31.0 CPython/3.10.13 Linux/5.15.0-92-generic ubuntu/22.04.2 glibc/2.35 solver/libmamba conda-libmamba-solver/23.12.0 libmambapy/1.5.5
                UID:GID : 1004:1100
             netrc file : None
           offline mode : False
@garymm garymm added the bug Something isn't working label Jan 31, 2024
@Tobias-Fischer
Copy link
Contributor

I’m not sure what the conda forge policy is - if we build with AVX2 support we would break systems that don’t have it.

@hmaarrfk I think I remember you had some thoughts about this somewhere written down?

@h-vetinari
Copy link
Member

It recently became possible to build different variants against different CPU capabilities. But I'm not aware of anyone using this yet.

Xref conda-forge/conda-forge.github.io#1261

@traversaro
Copy link

Just for reference if anyone wants to work on this, note that at the moment if you enable the archspec builds, you may break the installation of the package when using micromamba (see mamba-org/mamba#3222).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants