From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Silencing upcoming warning about stack_base_ptr
Date: Thu, 17 Feb 2022 19:40:39 -0500
Message-ID: <3778788.1645144839@sss.pgh.pa.us> (raw)
In-Reply-To: <20220218001255.cb566si23kq5f64r@alap3.anarazel.de>
References: <3773792.1645141467@sss.pgh.pa.us>
<20220218001255.cb566si23kq5f64r@alap3.anarazel.de>
Andres Freund <andres@anarazel.de> writes:
> On 2022-02-17 18:44:27 -0500, Tom Lane wrote:
>> (that's visible now on buildfarm member caiman). We probably
>> should take some thought for silencing this before it starts
>> to be in people's faces during routine development.
> We could try using __builtin_frame_address(0) when available, presumably gcc
> won't warn about that...
Oh, I didn't know about that. Seems like a better option since
then we don't need any API changes at all. Maybe at some point
some non-gcc-alike will start delivering a comparable warning,
but then we could fall back to what I did here.
regards, tom lane
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: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, pgsql-hackers@lists.postgresql.org
Subject: Re: Silencing upcoming warning about stack_base_ptr
In-Reply-To: <3778788.1645144839@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox