Re: seawasp failing, maybe in glibc allocator
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Thomas Munro <thomas.munro@gmail.com>,
Fabien COELHO <coelho@cri.ensmp.fr>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-05-21T22:18:54Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > Interesting. I tried this with a slightly older LLVM checkout > (6f4f0afaa8ae), from 2021-04-20, contrib/ltree tests run without an > issue, even if I force everything to be jitted+inlined+optimized. The > git hash in the package version indicates the commit is from > 2021-05-20. Upgrading my local checkout to see whether I can repro the > problem. If I can we at least have a not too large bisection window... We know that seawasp was okay as of configure: using compiler=clang version 13.0.0 (https://github.com/llvm/llvm-project.git f22d3813850f9e87c5204df6844a93b8c5db7730) and not okay as of configure: using compiler=clang version 13.0.0 (https://github.com/llvm/llvm-project.git 0e8f5e4a6864839d2292ec1ddfe48b6178c01f85) so that should correspond to a window of about a week, if I gather Fabien's update strategy correctly. regards, tom lane
Commits
-
Prepare for forthcoming LLVM 13 API change.
- 6ada4fd06666 11.13 landed
- 47d22649e6a2 12.8 landed
- d9c05a9ec493 13.4 landed
- 9b4e4cfe66ff 14.0 landed