Re: Defend against -ffast-math in meson builds

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Defend against -ffast-math in meson builds
Date: 2026-03-11 18:03:28
Message-ID: 3757.1773252208@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> writes:
> But still, I'm not sure the code-level guard is enough for meson. I think we
> need to put a guard in meson.build for the "oddity" described in [1]:

> it compiles fine with CFLAGS="-ffast-math" CC="gcc" meson setup meson_build but
> produces issues during the regression tests.

> I just had a closer look and it looks like that the reason is that it's being
> added at link time:

> $ cat meson_build/build.ninja | grep LINK_ARGS | grep -c "ffast-math"
> 254

Oy. Surely that is a meson bug? AFAICS most of the effects of
-ffast-math should occur at compile time. Perhaps it also results
in linking a different version of libm, but that's not everything.
So just transposing it into link flags is not okay.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexandre Felipe 2026-03-11 18:03:34 Re: Addressing buffer private reference count scalability issue
Previous Message Sami Imseih 2026-03-11 17:59:05 Re: another autovacuum scheduling thread