| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | ma lz <ma100(at)hotmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: strict-aliasing warning |
| Date: | 2025-12-10 06:44:29 |
| Message-ID: | aTkWzeR9HoIaUKQf@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Colin 't Hart | 2025-12-10 11:43:01 | pgBackrest and newer timelines |
| Previous Message | Adrian Klaver | 2025-12-10 03:04:23 | Re: strict-aliasing warning |