diff options
| author | Thomas Munro | 2025-12-30 01:11:37 +0000 |
|---|---|---|
| committer | Thomas Munro | 2025-12-30 01:34:32 +0000 |
| commit | 7da9d8f2db655eefba8757a66097bfabd3660a82 (patch) | |
| tree | a5406153a31762ced6d49628efd2a1cd1325edc5 /doc/src/FAQ.html | |
| parent | bd3e3e9e56830e1b1448b559743b0f0a90a6e38d (diff) | |
REL_18_STABLE and master have commit ee485912, so they always use the
newer LLVM opaque pointer functions. Drop -Wno-deprecated-declarations
(commit a56e7b660) for code under jit/llvm in those branches, to catch
any new deprecation warnings that arrive in future version of LLVM.
Older branches continued to use functions marked deprecated in LLVM 14
and 15 (ie switched to the newer functions only for LLVM 16+), as a
precaution against unforeseen compatibility problems with bitcode
already shipped. In those branches, the comment about warning
suppression is updated to explain that situation better. In theory we
could suppress warnings only for LLVM 14 and 15 specifically, but that
isn't done here.
Backpatch-through: 14
Reported-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/1407185.1766682319%40sss.pgh.pa.us
Diffstat (limited to 'doc/src/FAQ.html')
0 files changed, 0 insertions, 0 deletions