GitLab

at 2025-11-10T05:07:47-08:00

Fix #453:  Use correct flags when running the analyzer

Merge branch 'issue-453-update-make-options-for-analyzer' into 'master'

Fix #453:  Use correct flags when running the analyzer

Closes #453

See merge request cmucl/cmucl!332
   tags:

     - linux

   artifacts:

+    when: always

     paths:

       - analyzer.log

   needs:

     # console.  If someday there's less or no output, we can consider

     # having the logs go to the console too.

     - make -C build-4/lisp clean

-    # From

-    # https://docs.gitlab.com/ci/yaml/script/#ignore-non-zero-exit-codes

-    #

-    # If the analyzer fails, we still want the logs to be saved.  So

-    # ignore the failure, but also print a message so we know

-    # something happened.

-    - exit_code=0

-    - make -C build-4/lisp CFLAGS=-fanalyzer > analyzer.log 2>&1 || exit_code=$?

-    - if [ $exit_code -ne 0 ]; then echo "Analyzer failed with code $exit_code"; fi;

+    - make -C build-4/lisp ANALYZER=-fanalyzer > analyzer.log 2>&1

 #### OpenSUSE jobs ####

 opensuse:install:

 CFLAGS += $(COPT)

 CPPFLAGS += -m32

 CFLAGS += -rdynamic  -march=pentium4 -mfpmath=sse -mtune=generic

-CFLAGS += -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64

+# ANALYZER flag should be set to -fanalyzer when doing the CI builds

+# for the C static analyzer.

+CFLAGS += -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 $(ANALYZER)

 UNDEFSYMPATTERN = -Xlinker -u -Xlinker &

 ASSEM_SRC +=  linux-stubs.S

Raymond Toy pushed to branch master at cmucl / cmucl

Commits:

2 changed files:

Changes: