Re: pgsql: Avoid unsatisfied-external-reference errors in static inlines.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Avoid unsatisfied-external-reference errors in static inlines.
Date: 2022-07-14 15:19:06
Message-ID: 2833354.1657811946@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
> It seems that -fkeep-inline-functions is more demanding than what wrasse
> is running on. I need the attached patch to get it to build cleanly.

Interesting. I'm not entirely clear on which external references
cause wrasse to spit up.

> I think this would be good to apply so that this method of checking
> inline functions is available in the future.

+1

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2022-07-14 16:09:21 pgsql: doc: mention the pg_locks lock names in parentheses
Previous Message Peter Eisentraut 2022-07-14 14:48:25 Re: pgsql: Avoid unsatisfied-external-reference errors in static inlines.