From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Erik Rijkers <er(at)xs4all(dot)nl> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: gcc 12.1.0 warning |
Date: | 2022-05-06 14:46:20 |
Message-ID: | 2891033.1651848380@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Erik Rijkers <er(at)xs4all(dot)nl> writes:
> Not sure if these compiler-mutterings are worth reporting but I guess
> we're trying to get a silent compile.
> System: Debian 4.9.303-1 (2022-03-07) x86_64 GNU/Linux
> Compiling with gcc 12.1.0 causes the below 'warning' and 'note'.
> Compiling with --enable-cassert --enable-debug is silent, no warnings)
> In function ‘guc_var_compare’,
> inlined from ‘bsearch’ at
> /usr/include/x86_64-linux-gnu/bits/stdlib-bsearch.h:33:23,
> inlined from ‘find_option’ at guc.c:5649:35:
> guc.c:5736:38: warning: array subscript ‘const struct config_generic[0]’
> is partly outside array bounds of ‘const char[8]’ [-Warray-bounds]
> 5736 | return guc_name_compare(confa->name, confb->name);
> | ~~~~~^~~~~~
I'd call that a compiler bug.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2022-05-06 15:27:11 | Re: make MaxBackends available in _PG_init |
Previous Message | Tom Lane | 2022-05-06 14:43:21 | Re: make MaxBackends available in _PG_init |