| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Silencing upcoming warning about stack_base_ptr |
| Date: | 2022-02-18 00:40:39 |
| Message-ID: | 3778788.1645144839@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-02-18 01:18:51 | Re: adding 'zstd' as a compression algorithm |
| Previous Message | Andres Freund | 2022-02-18 00:34:34 | Re: Race conditions in 019_replslot_limit.pl |