| 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: New string-truncation warnings from GCC 15 |
| Date: | 2025-09-17 00:08:19 |
| Message-ID: | 1413298.1758067699@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2025-09-16 18:48:07 -0400, Tom Lane wrote:
>> It's not clear to me how well this approach will play with
>> non-GCC compilers.
> I'd assume we'd do something like
> #if has_attribute(nonstring)
> #define pg_nonstring __attribute__((nonstring))
> #else
> ...
> #define pg_nonstring
> #endif
> I can't really imagine that causing issues for other compilers...
Well, it wouldn't cause build failures, but perhaps it might fail
to silence comparable warnings from other compilers? This is
hypothetical of course, I don't know of any such case today.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2025-09-17 00:26:11 | Re: Fix missing EvalPlanQual recheck for TID scans |
| Previous Message | Álvaro Herrera | 2025-09-16 23:42:29 | Re: REPACK and naming |