From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: "Thomas Huth" <thuth@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>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v3] meson: Use -fno-sanitize=function when available
Date: Fri, 16 Aug 2024 16:12:41 +0900 [thread overview]
Message-ID: <337e647e-3edf-475c-8e37-de3d28b30340@daynix.com> (raw)
In-Reply-To: <3d417232-ba66-4781-8278-a6a31987b54c@redhat.com>
On 2024/08/16 16:03, Thomas Huth wrote:
> On 16/08/2024 08.22, Akihiko Odaki wrote:
>> Commit 23ef50ae2d0c (".gitlab-ci.d/buildtest.yml: Use
>> -fno-sanitize=function in the clang-system job") adds
>> -fno-sanitize=function for the CI but doesn't add the flag in the
>> other context. Add it to meson.build for such. It is not removed from
>> .gitlab-ci.d/buildtest.yml because -fno-sanitize=function in meson.build
>> does not affect --extra-cflags due to argument ordering.
>>
>> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
>> ---
>> Changes in v3:
>> - I was not properly dropping the change of .gitlab-ci.d/buildtest.yml
>> but only updated the message. v3 fixes this. (Thomas Huth)
>> - Link to v2:
>> https://lore.kernel.org/r/20240729-function-v2-1-2401ab18b30b@daynix.com
>>
>> Changes in v2:
>> - Dropped the change of: .gitlab-ci.d/buildtest.yml
>> - Link to v1:
>> https://lore.kernel.org/r/20240714-function-v1-1-cc2acb4171ba@daynix.com
>> ---
>> meson.build | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/meson.build b/meson.build
>> index 5613b62a4f42..a4169c572ba9 100644
>> --- a/meson.build
>> +++ b/meson.build
>> @@ -609,6 +609,7 @@ if host_os != 'openbsd' and \
>> endif
>> qemu_common_flags += cc.get_supported_arguments(hardening_flags)
>> +qemu_common_flags +=
>> cc.get_supported_arguments('-fno-sanitize=function')
>
> As I mentioned in my last mail: I think it would make sense to move this
> at the end of the "if get_option('tsan')" block in meson.build, since
> this apparently only fixes the use of "--enable-sanitizers", and cannot
> fix the "--extra-cflags" that a user might have specified?
Sorry, I missed it. It cannot fix --extra-cflags, but it should be able
to fix compiler flags specified by compiler distributor.
Regards,
Akihiko Odaki
next prev parent reply other threads:[~2024-08-16 7:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 6:22 [PATCH v3] meson: Use -fno-sanitize=function when available Akihiko Odaki
2024-08-16 7:03 ` Thomas Huth
2024-08-16 7:12 ` Akihiko Odaki [this message]
2024-08-16 7:27 ` Thomas Huth
2024-08-16 7:30 ` Akihiko Odaki
2024-08-16 8:03 ` Thomas Huth
2024-08-16 8:21 ` Akihiko Odaki
2024-08-16 8:24 ` Thomas Huth
2024-08-16 8:27 ` Akihiko Odaki
2024-08-16 8:46 ` Richard Henderson
2024-08-16 8:51 ` Akihiko Odaki
2024-08-16 8:51 ` Thomas Huth
2024-08-16 8:05 ` 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=337e647e-3edf-475c-8e37-de3d28b30340@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@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).