From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
Akihiko Odaki <akihiko.odaki@daynix.com>
Subject: Re: [PATCH] io/channel-socket: Fix -fsanitize=undefined problem with latest Clang
Date: Mon, 3 Jun 2024 18:55:00 +0100 [thread overview]
Message-ID: <Zl4DdL1Cwiy-GuCj@redhat.com> (raw)
In-Reply-To: <8734pthqc8.fsf@draig.linaro.org>
On Mon, Jun 03, 2024 at 06:46:15PM +0100, Alex Bennée wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > On Mon, Jun 03, 2024 at 03:47:55PM +0100, Alex Bennée wrote:
> >> Thomas Huth <thuth@redhat.com> writes:
> >>
> >> > Casting function pointers from one type to another causes undefined
> >> > behavior errors when compiling with -fsanitize=undefined with Clang
> >> > v18:
> >>
> >> Queued to testing/next, thanks.
> >
> > Please remove, as I don't think this is a viable approach to the
> > problem
>
> Ok - I'll drop it.
>
> I still have:
>
> .gitlab-ci.d/buildtest.yml: Use -fno-sanitize=function in the clang-system job
>
> to prevent the CI failures.
Yes, that's good.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2024-06-03 17:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 13:31 [PATCH] io/channel-socket: Fix -fsanitize=undefined problem with latest Clang Thomas Huth
2024-05-29 13:52 ` Philippe Mathieu-Daudé
2024-05-29 13:53 ` Peter Maydell
2024-06-03 12:48 ` Daniel P. Berrangé
2024-06-03 14:38 ` Thomas Huth
2024-06-03 14:49 ` Daniel P. Berrangé
2024-06-03 14:58 ` Peter Maydell
2024-06-03 15:12 ` Peter Maydell
2024-06-03 15:52 ` Daniel P. Berrangé
2024-06-03 15:55 ` Thomas Huth
2024-06-03 14:47 ` Alex Bennée
2024-06-03 14:50 ` Daniel P. Berrangé
2024-06-03 17:46 ` Alex Bennée
2024-06-03 17:55 ` Daniel P. Berrangé [this message]
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=Zl4DdL1Cwiy-GuCj@redhat.com \
--to=berrange@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@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).