From: Daniele Buono <dbuono@linux.vnet.ibm.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/2] gitlab-ci.yml: Add jobs to test CFI
Date: Tue, 2 Mar 2021 11:31:54 -0500 [thread overview]
Message-ID: <a4f78c9c-3a42-13dc-f095-16144d09ca6b@linux.vnet.ibm.com> (raw)
In-Reply-To: <YD5b74uynDvWUySy@redhat.com>
On 3/2/2021 10:38 AM, Daniel P. Berrangé wrote:
> Is this scenario going to upset CFI, or is it happy that 'void *'
> is compatible with 'mytype *', and ok with the intermediate casts
> to/from GCallback ?
This is a valid scenario. LLVM does offer the ability of considering all
pointer types compatible, and it is being enabled in QEMU. So void* is
compatible to any type* and that would not be considered a fault.
Intermediate casts are also fine since you are just passing the pointer
but not using it. The check will happen only when the function is
called, at which point it was cast back to something compatible.
next prev parent reply other threads:[~2021-03-02 16:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 15:21 [PATCH v2 0/2] gitlab-ci.yml: Add jobs to test CFI Daniele Buono
2021-02-26 15:21 ` [PATCH v2 1/2] gitlab-ci.yml: Allow custom # of parallel linkers Daniele Buono
2021-02-26 15:21 ` [PATCH v2 2/2] gitlab-ci.yml: Add jobs to test CFI flags Daniele Buono
2021-03-01 10:06 ` [PATCH v2 0/2] gitlab-ci.yml: Add jobs to test CFI Daniel P. Berrangé
2021-03-01 14:59 ` Daniele Buono
2021-03-01 15:08 ` Daniel P. Berrangé
2021-03-01 20:39 ` Daniele Buono
2021-03-02 10:30 ` Daniel P. Berrangé
2021-03-02 13:18 ` Daniele Buono
2021-03-02 15:38 ` Daniel P. Berrangé
2021-03-02 16:31 ` Daniele Buono [this message]
2021-03-02 16:40 ` Daniel P. Berrangé
2021-03-02 21:01 ` Daniele Buono
2021-03-03 10:04 ` Daniel P. Berrangé
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=a4f78c9c-3a42-13dc-f095-16144d09ca6b@linux.vnet.ibm.com \
--to=dbuono@linux.vnet.ibm.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).