pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Use appropriate -Wno-warning switches when compiling bitcode. 5+ messages / 1 participants [nested] [flat]
* pgsql: Use appropriate -Wno-warning switches when compiling bitcode. @ 2021-11-18 19:50 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 5+ messages in thread From: Tom Lane @ 2021-11-18 19:50 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use appropriate -Wno-warning switches when compiling bitcode. We use "clang" to compile bitcode files for LLVM inlining. That might be different from the build's main C compiler, so it needs its own set of compiler flags. To simplify configure, we don't bother adding any -W switches to that flag set; there's little need since the main build will show us any warnings. However, if we don't want to see unwanted warnings, we still have to add any -Wno-warning switches we'd normally use with clang. This escaped notice before commit 9ff47ea41, which tried to add -Wno-compound-token-split-by-macro; buildfarm animals using mismatched CC and CLANG still showed those warnings. I'm not sure why we never saw any effects from the lack of -Wno-unused-command-line-argument (maybe that's only activated by -Wall?). clang does not currently support -Wno-format-truncation or -Wno-stringop-truncation, although in the interests of future-proofing and consistency I included tests for those. Back-patch to v11 where we started building bitcode files. Discussion: https://postgr.es/m/2921539.1637254619@sss.pgh.pa.us Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/276517a96484f9e39a7a1095ab39fa76ef1ee8cc Modified Files -------------- configure | 194 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++--- configure.ac | 46 +++++++++++--- 2 files changed, 222 insertions(+), 18 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Use appropriate -Wno-warning switches when compiling bitcode. @ 2021-11-18 19:50 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 5+ messages in thread From: Tom Lane @ 2021-11-18 19:50 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use appropriate -Wno-warning switches when compiling bitcode. We use "clang" to compile bitcode files for LLVM inlining. That might be different from the build's main C compiler, so it needs its own set of compiler flags. To simplify configure, we don't bother adding any -W switches to that flag set; there's little need since the main build will show us any warnings. However, if we don't want to see unwanted warnings, we still have to add any -Wno-warning switches we'd normally use with clang. This escaped notice before commit 9ff47ea41, which tried to add -Wno-compound-token-split-by-macro; buildfarm animals using mismatched CC and CLANG still showed those warnings. I'm not sure why we never saw any effects from the lack of -Wno-unused-command-line-argument (maybe that's only activated by -Wall?). clang does not currently support -Wno-format-truncation or -Wno-stringop-truncation, although in the interests of future-proofing and consistency I included tests for those. Back-patch to v11 where we started building bitcode files. Discussion: https://postgr.es/m/2921539.1637254619@sss.pgh.pa.us Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/ed1c261a00e51f7f216911df2278827ba8cc211f Modified Files -------------- configure | 194 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++--- configure.ac | 46 +++++++++++--- 2 files changed, 222 insertions(+), 18 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Use appropriate -Wno-warning switches when compiling bitcode. @ 2021-11-18 19:50 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 5+ messages in thread From: Tom Lane @ 2021-11-18 19:50 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use appropriate -Wno-warning switches when compiling bitcode. We use "clang" to compile bitcode files for LLVM inlining. That might be different from the build's main C compiler, so it needs its own set of compiler flags. To simplify configure, we don't bother adding any -W switches to that flag set; there's little need since the main build will show us any warnings. However, if we don't want to see unwanted warnings, we still have to add any -Wno-warning switches we'd normally use with clang. This escaped notice before commit 9ff47ea41, which tried to add -Wno-compound-token-split-by-macro; buildfarm animals using mismatched CC and CLANG still showed those warnings. I'm not sure why we never saw any effects from the lack of -Wno-unused-command-line-argument (maybe that's only activated by -Wall?). clang does not currently support -Wno-format-truncation or -Wno-stringop-truncation, although in the interests of future-proofing and consistency I included tests for those. Back-patch to v11 where we started building bitcode files. Discussion: https://postgr.es/m/2921539.1637254619@sss.pgh.pa.us Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/77c8892a1989d91d8f1c9eb988b3c27ddad0ea07 Modified Files -------------- configure | 194 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++--- configure.in | 46 +++++++++++--- 2 files changed, 222 insertions(+), 18 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Use appropriate -Wno-warning switches when compiling bitcode. @ 2021-11-18 19:50 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 5+ messages in thread From: Tom Lane @ 2021-11-18 19:50 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use appropriate -Wno-warning switches when compiling bitcode. We use "clang" to compile bitcode files for LLVM inlining. That might be different from the build's main C compiler, so it needs its own set of compiler flags. To simplify configure, we don't bother adding any -W switches to that flag set; there's little need since the main build will show us any warnings. However, if we don't want to see unwanted warnings, we still have to add any -Wno-warning switches we'd normally use with clang. This escaped notice before commit 9ff47ea41, which tried to add -Wno-compound-token-split-by-macro; buildfarm animals using mismatched CC and CLANG still showed those warnings. I'm not sure why we never saw any effects from the lack of -Wno-unused-command-line-argument (maybe that's only activated by -Wall?). clang does not currently support -Wno-format-truncation or -Wno-stringop-truncation, although in the interests of future-proofing and consistency I included tests for those. Back-patch to v11 where we started building bitcode files. Discussion: https://postgr.es/m/2921539.1637254619@sss.pgh.pa.us Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/f5e3fab4333709d586fc8520025782b2a9d72c3a Modified Files -------------- configure | 194 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++--- configure.in | 46 +++++++++++--- 2 files changed, 222 insertions(+), 18 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Use appropriate -Wno-warning switches when compiling bitcode. @ 2021-11-18 19:50 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 5+ messages in thread From: Tom Lane @ 2021-11-18 19:50 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Use appropriate -Wno-warning switches when compiling bitcode. We use "clang" to compile bitcode files for LLVM inlining. That might be different from the build's main C compiler, so it needs its own set of compiler flags. To simplify configure, we don't bother adding any -W switches to that flag set; there's little need since the main build will show us any warnings. However, if we don't want to see unwanted warnings, we still have to add any -Wno-warning switches we'd normally use with clang. This escaped notice before commit 9ff47ea41, which tried to add -Wno-compound-token-split-by-macro; buildfarm animals using mismatched CC and CLANG still showed those warnings. I'm not sure why we never saw any effects from the lack of -Wno-unused-command-line-argument (maybe that's only activated by -Wall?). clang does not currently support -Wno-format-truncation or -Wno-stringop-truncation, although in the interests of future-proofing and consistency I included tests for those. Back-patch to v11 where we started building bitcode files. Discussion: https://postgr.es/m/2921539.1637254619@sss.pgh.pa.us Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/dff01e40496122a9a4b3fb5a47ed5d124d32aff9 Modified Files -------------- configure | 194 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++--- configure.in | 46 +++++++++++--- 2 files changed, 222 insertions(+), 18 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2021-11-18 19:50 UTC | newest] Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2021-11-18 19:50 pgsql: Use appropriate -Wno-warning switches when compiling bitcode. Tom Lane <tgl@sss.pgh.pa.us> 2021-11-18 19:50 pgsql: Use appropriate -Wno-warning switches when compiling bitcode. Tom Lane <tgl@sss.pgh.pa.us> 2021-11-18 19:50 pgsql: Use appropriate -Wno-warning switches when compiling bitcode. Tom Lane <tgl@sss.pgh.pa.us> 2021-11-18 19:50 pgsql: Use appropriate -Wno-warning switches when compiling bitcode. Tom Lane <tgl@sss.pgh.pa.us> 2021-11-18 19:50 pgsql: Use appropriate -Wno-warning switches when compiling bitcode. 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