gha: Dropped explicit CFLAGS from clang testing in CI

Thanks to yamt, GCC-specific flags should now be disabled if compiling
with clang. Dropping the explicit flags also doubles as a test that the
NO_GCC inference works.
This commit is contained in:
Christopher Haster
2025-05-07 23:45:29 -05:00
parent bff4dfd1b1
commit 0115cf6b74

View File

@@ -454,8 +454,7 @@ jobs:
TESTFLAGS="$TESTFLAGS --valgrind --context=1024 -Gdefault -Pnone" \ TESTFLAGS="$TESTFLAGS --valgrind --context=1024 -Gdefault -Pnone" \
make test make test
# test that compilation is warning free under clang # compile/run with Clang, mostly to check for Clang-specific warnings
# run with Clang, mostly to check for Clang-specific warnings
test-clang: test-clang:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
@@ -469,12 +468,8 @@ jobs:
python3 --version python3 --version
- name: test-clang - name: test-clang
run: | run: |
# override CFLAGS since Clang does not support -fcallgraph-info CC=clang \
# and -ftrack-macro-expansions make test
make \
CC=clang \
CFLAGS="$CFLAGS -MMD -g3 -I. -std=c99 -Wall -Wextra -pedantic" \
test
# run benchmarks # run benchmarks
# #