pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Silence another gcc 11 warning. 10+ messages / 1 participants [nested] [flat]
* pgsql: Silence another gcc 11 warning. @ 2021-01-28 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 10+ messages in thread From: Tom Lane @ 2021-01-28 22:19 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Silence another gcc 11 warning. Per buildfarm and local experimentation, bleeding-edge gcc isn't convinced that the MemSet in reorder_function_arguments() is safe. Shut it up by adding an explicit check that pronargs isn't negative, and by changing MemSet to memset. (It appears that either change is enough to quiet the warning at -O2, but let's do both to be sure.) Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/1046dbedde2fc3fe55f007ff3255ab65ab98f858 Modified Files -------------- src/backend/optimizer/util/clauses.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 10+ messages in thread
* pgsql: Silence another gcc 11 warning. @ 2021-01-28 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 10+ messages in thread From: Tom Lane @ 2021-01-28 22:19 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Silence another gcc 11 warning. Per buildfarm and local experimentation, bleeding-edge gcc isn't convinced that the MemSet in reorder_function_arguments() is safe. Shut it up by adding an explicit check that pronargs isn't negative, and by changing MemSet to memset. (It appears that either change is enough to quiet the warning at -O2, but let's do both to be sure.) Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/4a9ce085ab30ad01ffe03eb1743da82b1be280c1 Modified Files -------------- src/backend/optimizer/util/clauses.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 10+ messages in thread
* pgsql: Silence another gcc 11 warning. @ 2021-01-28 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 10+ messages in thread From: Tom Lane @ 2021-01-28 22:19 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Silence another gcc 11 warning. Per buildfarm and local experimentation, bleeding-edge gcc isn't convinced that the MemSet in reorder_function_arguments() is safe. Shut it up by adding an explicit check that pronargs isn't negative, and by changing MemSet to memset. (It appears that either change is enough to quiet the warning at -O2, but let's do both to be sure.) Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/22f71a6e1d76c08f3f2a11459ae7a391ea223a97 Modified Files -------------- src/backend/optimizer/util/clauses.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 10+ messages in thread
* pgsql: Silence another gcc 11 warning. @ 2021-01-28 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 10+ messages in thread From: Tom Lane @ 2021-01-28 22:19 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Silence another gcc 11 warning. Per buildfarm and local experimentation, bleeding-edge gcc isn't convinced that the MemSet in reorder_function_arguments() is safe. Shut it up by adding an explicit check that pronargs isn't negative, and by changing MemSet to memset. (It appears that either change is enough to quiet the warning at -O2, but let's do both to be sure.) Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/289ef386dff6662b1c1cf90d0666a3863bcf5ba8 Modified Files -------------- src/backend/optimizer/util/clauses.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 10+ messages in thread
* pgsql: Silence another gcc 11 warning. @ 2021-01-28 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 10+ messages in thread From: Tom Lane @ 2021-01-28 22:19 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Silence another gcc 11 warning. Per buildfarm and local experimentation, bleeding-edge gcc isn't convinced that the MemSet in reorder_function_arguments() is safe. Shut it up by adding an explicit check that pronargs isn't negative, and by changing MemSet to memset. (It appears that either change is enough to quiet the warning at -O2, but let's do both to be sure.) Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/c4484232ed3f17c270621eb8ffb974d85023b9ea Modified Files -------------- src/backend/optimizer/util/clauses.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 10+ messages in thread
* pgsql: Silence another gcc 11 warning. @ 2021-01-28 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 10+ messages in thread From: Tom Lane @ 2021-01-28 22:19 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Silence another gcc 11 warning. Per buildfarm and local experimentation, bleeding-edge gcc isn't convinced that the MemSet in reorder_function_arguments() is safe. Shut it up by adding an explicit check that pronargs isn't negative, and by changing MemSet to memset. (It appears that either change is enough to quiet the warning at -O2, but let's do both to be sure.) Branch ------ REL9_6_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/ea3164aae4b2d2edfb1dc3bd450bfed86d3266ea Modified Files -------------- src/backend/optimizer/util/clauses.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 10+ messages in thread
* pgsql: Silence another gcc 11 warning. @ 2021-01-28 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 10+ messages in thread From: Tom Lane @ 2021-01-28 22:19 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Silence another gcc 11 warning. Per buildfarm and local experimentation, bleeding-edge gcc isn't convinced that the MemSet in reorder_function_arguments() is safe. Shut it up by adding an explicit check that pronargs isn't negative, and by changing MemSet to memset. (It appears that either change is enough to quiet the warning at -O2, but let's do both to be sure.) Branch ------ REL9_5_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/d777e27c80f83e1177393641b99b1c7c4b19af17 Modified Files -------------- src/backend/optimizer/util/clauses.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 10+ messages in thread
* pgsql: Silence another gcc 11 warning. @ 2021-12-13 05:09 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 10+ messages in thread From: Tom Lane @ 2021-12-13 05:09 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Silence another gcc 11 warning. Per buildfarm and local experimentation, bleeding-edge gcc isn't convinced that the MemSet in reorder_function_arguments() is safe. Shut it up by adding an explicit check that pronargs isn't negative, and by changing MemSet to memset. (It appears that either change is enough to quiet the warning at -O2, but let's do both to be sure.) This back-patches commit 1046dbedd into out-of-support branches, pursuant to newly-established project policy. The point is to suppress scary-looking warnings so that people building these branches needn't expend brain cells verifying that it's safe to ignore the warnings. Discussion: https://postgr.es/m/d0316012-ece7-7b7e-2d36-9c38cb77cb3b@enterprisedb.com Branch ------ REL9_4_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/0af208402d0a5cede0e8c9007112233032dab639 Modified Files -------------- src/backend/optimizer/util/clauses.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 10+ messages in thread
* pgsql: Silence another gcc 11 warning. @ 2021-12-13 05:09 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 10+ messages in thread From: Tom Lane @ 2021-12-13 05:09 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Silence another gcc 11 warning. Per buildfarm and local experimentation, bleeding-edge gcc isn't convinced that the MemSet in reorder_function_arguments() is safe. Shut it up by adding an explicit check that pronargs isn't negative, and by changing MemSet to memset. (It appears that either change is enough to quiet the warning at -O2, but let's do both to be sure.) This back-patches commit 1046dbedd into out-of-support branches, pursuant to newly-established project policy. The point is to suppress scary-looking warnings so that people building these branches needn't expend brain cells verifying that it's safe to ignore the warnings. Discussion: https://postgr.es/m/d0316012-ece7-7b7e-2d36-9c38cb77cb3b@enterprisedb.com Branch ------ REL9_3_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/a1fe82d98745483b250ab61c3bc903931dc966ba Modified Files -------------- src/backend/optimizer/util/clauses.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 10+ messages in thread
* pgsql: Silence another gcc 11 warning. @ 2021-12-13 05:09 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 10+ messages in thread From: Tom Lane @ 2021-12-13 05:09 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Silence another gcc 11 warning. Per buildfarm and local experimentation, bleeding-edge gcc isn't convinced that the MemSet in reorder_function_arguments() is safe. Shut it up by adding an explicit check that pronargs isn't negative, and by changing MemSet to memset. (It appears that either change is enough to quiet the warning at -O2, but let's do both to be sure.) This back-patches commit 1046dbedd into out-of-support branches, pursuant to newly-established project policy. The point is to suppress scary-looking warnings so that people building these branches needn't expend brain cells verifying that it's safe to ignore the warnings. Discussion: https://postgr.es/m/d0316012-ece7-7b7e-2d36-9c38cb77cb3b@enterprisedb.com Branch ------ REL9_2_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/265b96a96af21958989efeb7ee4b3c0129f75ae5 Modified Files -------------- src/backend/optimizer/util/clauses.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 10+ messages in thread
end of thread, other threads:[~2021-12-13 05:09 UTC | newest] Thread overview: 10+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2021-01-28 22:19 pgsql: Silence another gcc 11 warning. Tom Lane <tgl@sss.pgh.pa.us> 2021-01-28 22:19 pgsql: Silence another gcc 11 warning. Tom Lane <tgl@sss.pgh.pa.us> 2021-01-28 22:19 pgsql: Silence another gcc 11 warning. Tom Lane <tgl@sss.pgh.pa.us> 2021-01-28 22:19 pgsql: Silence another gcc 11 warning. Tom Lane <tgl@sss.pgh.pa.us> 2021-01-28 22:19 pgsql: Silence another gcc 11 warning. Tom Lane <tgl@sss.pgh.pa.us> 2021-01-28 22:19 pgsql: Silence another gcc 11 warning. Tom Lane <tgl@sss.pgh.pa.us> 2021-01-28 22:19 pgsql: Silence another gcc 11 warning. Tom Lane <tgl@sss.pgh.pa.us> 2021-12-13 05:09 pgsql: Silence another gcc 11 warning. Tom Lane <tgl@sss.pgh.pa.us> 2021-12-13 05:09 pgsql: Silence another gcc 11 warning. Tom Lane <tgl@sss.pgh.pa.us> 2021-12-13 05:09 pgsql: Silence another gcc 11 warning. Tom Lane <tgl@sss.pgh.pa.us>
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