From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Wolfgang Walther <walther(at)technowledgy(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: Build with LTO / -flto on macOS |
Date: | 2024-07-19 15:21:05 |
Message-ID: | ZpqEYbkS2azrmiv3@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Re: Tom Lane
> I fear that #2 is actually a pretty serious concern. I think there
> are a lot of places where we've assumed semi-implicitly that
> compilation file boundaries are optimization barriers, particularly
> around stuff like LWLocks and semaphores. I don't really want to
> spend time chasing obscure, irreproducible bugs that may appear when
> that assumption gets broken. I especially don't want to do it just
> because some packager has randomly decided to inject random build
> switches.
Ubuntu enabled -ftlo=auto by default in 22.04, so it has been around
for some time already.
$ dpkg-buildflags
CFLAGS=-g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=... -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=...
Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2024-07-19 15:32:06 | Re: Incremental backup from a streaming replication standby fails |
Previous Message | Jelte Fennema-Nio | 2024-07-19 15:16:19 | Re: Report search_path value back to the client. |