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

AVX512 Support #3776

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Commits on Jul 3, 2024

  1. Initial AVX512 Support

    CMake Changes:
    Added the AVX512F_SUPPORT flag to CMake. Set by checking
    if system supports AVX512F. If it doesn't it will not build (and therefore run) any of the AVX512 tests
    
    Added the target descriptions. Assumed that PKRU support also implies AVX512 support as I could find no information that said otherwise.
    
    Added gdb_avx512 test - sets 3 ZMM registers and reads them back in a gdb session of a replay to verify the contents.
    
    We place mask registers K0-K7 after ZMM31H internally, because this simplifies the logic that parses the XSAVE area. The target description we provide, takes this into account (and also places them last) so they come after the ZMM registers in the 'g' packet. GDB doesn't care so long as we do what we say in the target desc
    
    Changed test harness util.sh to also export TESTNAME variable as we may (I do at least) want to query from the python script what mode we are running in (64-bit/32-bit). See gdb_avx512.py for further info.
    theIDinside committed Jul 3, 2024
    Configuration menu
    Copy the full SHA
    e55907c View commit details
    Browse the repository at this point in the history
  2. Bug fix

    AVX512F support always returned true due to using -mavx512f as flag instead of -march=native to `try_compile`
    theIDinside committed Jul 3, 2024
    Configuration menu
    Copy the full SHA
    23fcaef View commit details
    Browse the repository at this point in the history