From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>
Subject: [PULL 08/12] .gitlab-ci.d/buildtest.yml: Use -fno-sanitize=function in the clang-system job
Date: Thu, 6 Jun 2024 12:50:43 +0100 [thread overview]
Message-ID: <20240606115047.421045-9-alex.bennee@linaro.org> (raw)
In-Reply-To: <20240606115047.421045-1-alex.bennee@linaro.org>
From: Thomas Huth <thuth@redhat.com>
The latest version of Clang (version 18 from Fedora 40) now reports
bad function pointer casts as undefined behavior. Unfortunately, we are
still doing this in quite a lot of places in the QEMU code and some of
them are not easy to fix. So for the time being, temporarily switch this
off in the failing clang-system job until all spots in the QEMU sources
have been tackled.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20240601070543.37786-4-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20240603175328.3823123-9-alex.bennee@linaro.org>
diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
index 91c57efded..0eec570310 100644
--- a/.gitlab-ci.d/buildtest.yml
+++ b/.gitlab-ci.d/buildtest.yml
@@ -432,6 +432,7 @@ clang-system:
IMAGE: fedora
CONFIGURE_ARGS: --cc=clang --cxx=clang++
--extra-cflags=-fsanitize=undefined --extra-cflags=-fno-sanitize-recover=undefined
+ --extra-cflags=-fno-sanitize=function
TARGETS: alpha-softmmu arm-softmmu m68k-softmmu mips64-softmmu s390x-softmmu
MAKE_CHECK_ARGS: check-qtest check-tcg
--
2.39.2
next prev parent reply other threads:[~2024-06-06 11:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 11:50 [PULL 00/12] testing cleanups (ci, vm, lcitool, ansible) Alex Bennée
2024-06-06 11:50 ` [PULL 01/12] ci: remove centos-steam-8 customer runner Alex Bennée
2024-06-06 11:50 ` [PULL 02/12] docs/devel: update references to centos to non-versioned container Alex Bennée
2024-06-06 11:50 ` [PULL 03/12] tests/vm: update centos.aarch64 image to 9 Alex Bennée
2024-06-06 11:50 ` [PULL 04/12] tests/vm: remove plain centos image Alex Bennée
2024-06-06 11:50 ` [PULL 05/12] scripts/ci: remove CentOS bits from common build-environment Alex Bennée
2024-06-06 11:50 ` [PULL 06/12] docs/ci: clean-up references for consistency Alex Bennée
2024-06-06 11:50 ` [PULL 07/12] tests/lcitool: Delete obsolete centos-stream-8.yml file Alex Bennée
2024-06-06 11:50 ` Alex Bennée [this message]
2024-06-06 11:50 ` [PULL 09/12] tests/lcitool: Bump to latest libvirt-ci and update Fedora and Alpine version Alex Bennée
2024-06-06 11:50 ` [PULL 10/12] tests/lcitool: Install mingw-w64-tools for the Windows cross-builds Alex Bennée
2024-06-06 11:50 ` [PULL 11/12] tests/lcitool: generate package lists for ansible Alex Bennée
2024-06-06 11:50 ` [PULL 12/12] scripts/ci: drive ubuntu/build-environment.yml from lcitool Alex Bennée
2024-06-06 18:54 ` [PULL 00/12] testing cleanups (ci, vm, lcitool, ansible) Richard Henderson
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=20240606115047.421045-9-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).