From acd2c0a8c55f9fe6d1604b332abf3001356bc3d0 Mon Sep 17 00:00:00 2001
From: Folkert de Vries <folkert@folkertdev.nl>
Date: Wed, 8 Jan 2025 16:55:15 +0100
Subject: [PATCH] don't use `target-cpu=native` for the benchmarks

It's an unfair advantage versus zlib-ng, and any changes we make to dynamically recognizing features would not get picked up by the benchmarks
---
 .github/workflows/bench.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/bench.yml b/.github/workflows/bench.yml
index b06809b..18ca168 100644
--- a/.github/workflows/bench.yml
+++ b/.github/workflows/bench.yml
@@ -45,7 +45,7 @@ jobs:
       - name: cargo build
         run: |
           . "$HOME/.cargo/env"
-          RUSTFLAGS="-Ctarget-cpu=native -Cllvm-args=-enable-dfa-jump-thread" cargo build --target ${{matrix.target}} -p test-libz-rs-sys --release --examples
+          RUSTFLAGS="-Cllvm-args=-enable-dfa-jump-thread" cargo build --target ${{matrix.target}} -p test-libz-rs-sys --release --examples
           cp target/${{matrix.target}}/release/examples/blogpost-compress .
           cp target/${{matrix.target}}/release/examples/blogpost-uncompress .
       - name: Benchmark