pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai 7+ messages / 1 participants [nested] [flat]
* pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai @ 2018-06-16 19:34 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2018-06-16 19:34 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use -Wno-format-truncation and -Wno-stringop-truncation, if available. gcc 8 has started emitting some warnings that are largely useless for our purposes, particularly since they complain about code following the project-standard coding convention that path names are assumed to be shorter than MAXPGPATH. Even if we make the effort to remove that assumption in some future release, the changes wouldn't get back-patched. Hence, just suppress these warnings, on compilers that have these switches. Backpatch to all supported branches. Discussion: https://postgr.es/m/1524563856.26306.9.camel@gunduz.org Branch ------ REL9_6_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/119290be6fe3bea12053042f5d3eaa135a260a52 Modified Files -------------- configure | 80 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ configure.in | 12 +++++++++ 2 files changed, 92 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai @ 2018-06-16 19:34 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2018-06-16 19:34 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use -Wno-format-truncation and -Wno-stringop-truncation, if available. gcc 8 has started emitting some warnings that are largely useless for our purposes, particularly since they complain about code following the project-standard coding convention that path names are assumed to be shorter than MAXPGPATH. Even if we make the effort to remove that assumption in some future release, the changes wouldn't get back-patched. Hence, just suppress these warnings, on compilers that have these switches. Backpatch to all supported branches. Discussion: https://postgr.es/m/1524563856.26306.9.camel@gunduz.org Branch ------ REL9_3_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/ec5547e563a85cb84fc186dd96c41a86c59cc7fa Modified Files -------------- configure | 130 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ configure.in | 12 ++++++ 2 files changed, 142 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai @ 2018-06-16 19:34 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2018-06-16 19:34 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use -Wno-format-truncation and -Wno-stringop-truncation, if available. gcc 8 has started emitting some warnings that are largely useless for our purposes, particularly since they complain about code following the project-standard coding convention that path names are assumed to be shorter than MAXPGPATH. Even if we make the effort to remove that assumption in some future release, the changes wouldn't get back-patched. Hence, just suppress these warnings, on compilers that have these switches. Backpatch to all supported branches. Discussion: https://postgr.es/m/1524563856.26306.9.camel@gunduz.org Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/e716585235b175de767d3b210f0a963457dfa77f Modified Files -------------- configure | 88 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ configure.in | 12 +++++++++ 2 files changed, 100 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai @ 2018-06-16 19:34 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2018-06-16 19:34 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use -Wno-format-truncation and -Wno-stringop-truncation, if available. gcc 8 has started emitting some warnings that are largely useless for our purposes, particularly since they complain about code following the project-standard coding convention that path names are assumed to be shorter than MAXPGPATH. Even if we make the effort to remove that assumption in some future release, the changes wouldn't get back-patched. Hence, just suppress these warnings, on compilers that have these switches. Backpatch to all supported branches. Discussion: https://postgr.es/m/1524563856.26306.9.camel@gunduz.org Branch ------ REL9_4_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/817d605e411faacec09f2f95f9749f8a23eb83b1 Modified Files -------------- configure | 80 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ configure.in | 12 +++++++++ 2 files changed, 92 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai @ 2018-06-16 19:34 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2018-06-16 19:34 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use -Wno-format-truncation and -Wno-stringop-truncation, if available. gcc 8 has started emitting some warnings that are largely useless for our purposes, particularly since they complain about code following the project-standard coding convention that path names are assumed to be shorter than MAXPGPATH. Even if we make the effort to remove that assumption in some future release, the changes wouldn't get back-patched. Hence, just suppress these warnings, on compilers that have these switches. Backpatch to all supported branches. Discussion: https://postgr.es/m/1524563856.26306.9.camel@gunduz.org Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/416e3e318cc42cfc36633ba3d1fde708cfa084af Modified Files -------------- configure | 80 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ configure.in | 12 +++++++++ 2 files changed, 92 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai @ 2018-06-16 19:34 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2018-06-16 19:34 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use -Wno-format-truncation and -Wno-stringop-truncation, if available. gcc 8 has started emitting some warnings that are largely useless for our purposes, particularly since they complain about code following the project-standard coding convention that path names are assumed to be shorter than MAXPGPATH. Even if we make the effort to remove that assumption in some future release, the changes wouldn't get back-patched. Hence, just suppress these warnings, on compilers that have these switches. Backpatch to all supported branches. Discussion: https://postgr.es/m/1524563856.26306.9.camel@gunduz.org Branch ------ REL9_5_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/14b69a53219716c642bc814b94ff2409a2c2c439 Modified Files -------------- configure | 80 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ configure.in | 12 +++++++++ 2 files changed, 92 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai @ 2021-12-12 21:46 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2021-12-12 21:46 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use -Wno-format-truncation and -Wno-stringop-truncation, if available. This back-patches commit e71658523 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. Also back-patch the adjacent test from commit 73b416b2e (Suppress clang's unhelpful gripes about -pthread switch being unused) and the necessary autoconf macro from fdea2530b. Discussion: https://postgr.es/m/d0316012-ece7-7b7e-2d36-9c38cb77cb3b@enterprisedb.com Branch ------ REL9_2_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/276c017f12fe6ecbd07bebaff00768ec34f2ea21 Modified Files -------------- config/c-compiler.m4 | 25 +++++++ configure | 196 +++++++++++++++++++++++++++++++++++++++++++++++++++ configure.in | 19 +++++ 3 files changed, 240 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2021-12-12 21:46 UTC | newest] Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2018-06-16 19:34 pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai Tom Lane <tgl@sss.pgh.pa.us> 2018-06-16 19:34 pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai Tom Lane <tgl@sss.pgh.pa.us> 2018-06-16 19:34 pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai Tom Lane <tgl@sss.pgh.pa.us> 2018-06-16 19:34 pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai Tom Lane <tgl@sss.pgh.pa.us> 2018-06-16 19:34 pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai Tom Lane <tgl@sss.pgh.pa.us> 2018-06-16 19:34 pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai Tom Lane <tgl@sss.pgh.pa.us> 2021-12-12 21:46 pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai 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