pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Use -Wno-format-truncation and -Wno-stringop-truncation, if avai
Date: 2018-06-16 19:34:30
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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/[email protected]

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/e716585235b175de767d3b210f0a963457dfa77f

Modified Files
--------------
configure | 88 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
configure.in | 12 +++++++++
2 files changed, 100 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2018-06-16 22:30:51 pgsql: Remove INCLUDE attributes section from docs.
Previous Message Tom Lane 2018-06-16 18:59:01 pgsql: Avoid unnecessary use of strncpy in a couple of places in ecpg.