From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: tarantool-patches@dev.tarantool.org, Sergey Kaplun <skaplun@tarantool.org>, Maxim Kokryashkin <m.kokryashkin@tarantool.org> Subject: [Tarantool-patches] [PATCH luajit 1/4][v2] ci: add a workflow for testing with AVX512 Date: Thu, 11 Apr 2024 16:22:02 +0300 [thread overview] Message-ID: <6777a43e3012332d04493f93d6afe7fb4156af1b.1712841312.git.sergeyb@tarantool.org> (raw) In-Reply-To: <cover.1712841312.git.sergeyb@tarantool.org> From: Sergey Bronnikov <sergeyb@tarantool.org> This commit adds a workflow for building and testing with enabled AVX512. Needed for tarantool/tarantool#9595 Related to tarantool/tarantool#6787 --- .github/actions/setup-linux/action.yml | 12 +++++ .github/workflows/avx512-build-testing.yml | 54 ++++++++++++++++++++++ test/LuaJIT-tests/lib/ffi/bit64.lua | 2 +- 3 files changed, 67 insertions(+), 1 deletion(-) create mode 100644 .github/workflows/avx512-build-testing.yml diff --git a/.github/actions/setup-linux/action.yml b/.github/actions/setup-linux/action.yml index f0171b83..19bdcfa2 100644 --- a/.github/actions/setup-linux/action.yml +++ b/.github/actions/setup-linux/action.yml @@ -17,3 +17,15 @@ runs: apt -y update apt -y install cmake gcc make ninja-build perl shell: bash + - name: Detect a presence of AVX512 + id: avx512_script + run: | + # Set avx512_support environment variable to 'true' when AVX512 + # is supported and 'false' otherwise. + # + # Normally `grep` has the exit status is 0 if a line is + # selected, 1 if no lines were selected, and 2 if an error + # occurred. + avx512_support=$(grep avx /proc/cpuinfo 2>&1 > /dev/null; [[ $? == 0 ]] && echo 0 || echo 1) + echo "avx512_support=$avx512_support" >> $GITHUB_OUTPUT + shell: bash diff --git a/.github/workflows/avx512-build-testing.yml b/.github/workflows/avx512-build-testing.yml new file mode 100644 index 00000000..d70fa661 --- /dev/null +++ b/.github/workflows/avx512-build-testing.yml @@ -0,0 +1,54 @@ +name: "AVX512 build testing" + +on: + push: + branches-ignore: + - '**-notest' + - 'upstream-**' + tags-ignore: + - '**' + +concurrency: + # An update of a developer branch cancels the previously + # scheduled workflow run for this branch. However, the default + # branch, and long-term branch (tarantool/release/2.11, + # tarantool/release/2.10, etc) workflow runs are never canceled. + # + # We use a trick here: define the concurrency group as 'workflow + # run ID' + # 'workflow run attempt' because it is a unique + # combination for any run. So it effectively discards grouping. + # + # XXX: we cannot use `github.sha` as a unique identifier because + # pushing a tag may cancel a run that works on a branch push + # event. + group: ${{ startsWith(github.ref, 'refs/heads/tarantool/') + && format('{0}-{1}', github.run_id, github.run_attempt) + || format('{0}-{1}', github.workflow, github.ref) }} + cancel-in-progress: true + +jobs: + test-avx512: + strategy: + fail-fast: false + runs-on: [self-hosted, regular, x86_64, Linux] + steps: + - uses: actions/checkout@v4 + with: + fetch-depth: 0 + submodules: recursive + - name: setup Linux + uses: ./.github/actions/setup-linux + - name: configure + if: needs.avx512_script.outputs.avx512_support == 0 + run: > + cmake -S . -B ${{ env.BUILDDIR }} + -G Ninja + -DCMAKE_BUILD_TYPE=RelWithDebInfo + -DCMAKE_C_FLAGS=-march=skylake-avx512 + -DCMAKE_C_COMPILER=gcc + - name: build + if: needs.avx512_script.outputs.avx512_support == 0 + run: cmake --build ${{ env.BUILDDIR }} --parallel + - name: run regression tests + if: needs.avx512_script.outputs.avx512_support == 0 + run: cmake --build ${{ env.BUILDDIR }} --parallel --target LuaJIT-test diff --git a/test/LuaJIT-tests/lib/ffi/bit64.lua b/test/LuaJIT-tests/lib/ffi/bit64.lua index d1b47bef..cf3a96eb 100644 --- a/test/LuaJIT-tests/lib/ffi/bit64.lua +++ b/test/LuaJIT-tests/lib/ffi/bit64.lua @@ -41,7 +41,7 @@ do --- tobit/band assorted C types end end -do --- tobit/band negative unsigned enum +do --- tobit/band negative unsigned enum -avx512 local x = ffi.new("uenum_t", -10) local y = tobit(x) local z = band(x) -- 2.34.1
next prev parent reply other threads:[~2024-04-11 15:25 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-11 13:22 [Tarantool-patches] [PATCH luajit 0/4][v2] Mach-O generation fixes Sergey Bronnikov via Tarantool-patches 2024-04-11 13:22 ` Sergey Bronnikov via Tarantool-patches [this message] 2024-04-12 10:27 ` [Tarantool-patches] [PATCH luajit 1/4][v2] ci: add a workflow for testing with AVX512 Sergey Kaplun via Tarantool-patches 2024-04-16 11:53 ` Sergey Bronnikov via Tarantool-patches 2024-04-18 8:24 ` Sergey Kaplun via Tarantool-patches 2024-05-05 12:29 ` Maxim Kokryashkin via Tarantool-patches 2024-06-14 13:55 ` Sergey Bronnikov via Tarantool-patches 2024-06-14 15:24 ` Sergey Bronnikov via Tarantool-patches 2024-04-11 13:22 ` [Tarantool-patches] [PATCH luajit 2/4][v2] test: introduce a helper read_file Sergey Bronnikov via Tarantool-patches 2024-04-12 10:47 ` Sergey Kaplun via Tarantool-patches 2024-04-16 12:02 ` Sergey Bronnikov via Tarantool-patches 2024-06-20 12:14 ` Sergey Bronnikov via Tarantool-patches 2024-04-11 13:22 ` [Tarantool-patches] [PATCH luajit 3/4][v2] OSX/iOS/ARM64: Fix generation of Mach-O object files Sergey Bronnikov via Tarantool-patches 2024-04-12 11:19 ` Sergey Kaplun via Tarantool-patches 2024-04-16 15:29 ` Sergey Bronnikov via Tarantool-patches 2024-06-13 15:50 ` Sergey Bronnikov via Tarantool-patches 2024-04-11 13:22 ` [Tarantool-patches] [PATCH luajit 4/4][v2] OSX/iOS/ARM64: Fix bytecode embedding in Mach-O object file Sergey Bronnikov via Tarantool-patches 2024-04-12 11:27 ` Sergey Kaplun via Tarantool-patches 2024-06-13 15:40 ` Sergey Bronnikov via Tarantool-patches 2024-06-13 15:47 ` Sergey Bronnikov via Tarantool-patches 2024-06-20 10:15 ` [Tarantool-patches] [PATCH luajit 0/4][v2] Mach-O generation fixes Sergey Kaplun via Tarantool-patches 2024-07-09 8:07 ` Sergey Kaplun via Tarantool-patches
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=6777a43e3012332d04493f93d6afe7fb4156af1b.1712841312.git.sergeyb@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=estetus@gmail.com \ --cc=m.kokryashkin@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 1/4][v2] ci: add a workflow for testing with AVX512' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox