public inbox for [email protected]
help / color / mirror / Atom feedFrom: Michael Paquier <[email protected]>
To: Adrian Klaver <[email protected]>
Cc: ma lz <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: strict-aliasing warning
Date: Wed, 10 Dec 2025 15:44:29 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <TY7PR01MB1485649F37F239834635A33B6F2A0A@TY7PR01MB14856.jpnprd01.prod.outlook.com>
<[email protected]>
On Tue, Dec 09, 2025 at 07:04:23PM -0800, Adrian Klaver wrote:
> On 12/9/25 18:27, ma lz wrote:
>> Don't use IsA may fix this problem
>
> Why is it a problem?
Well, I don't think that this has proved to be a problem until now in
the buildfarm. I doubt that it would be the only problematic area if
a new compiler flag is enforced by a buildfarm member, assuming that
we would add one but the bar is very high when it comes to that.
A 4-line message is short to present your arguments, what you are
trying to do, and why it could make sense in some way.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, 2-signature.asc)
download
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: strict-aliasing warning
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox