Re: seawasp failing, maybe in glibc allocator
От | Andres Freund |
---|---|
Тема | Re: seawasp failing, maybe in glibc allocator |
Дата | |
Msg-id | 20210521225701.kzmfzogrq7eqnz4p@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: seawasp failing, maybe in glibc allocator (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: seawasp failing, maybe in glibc allocator
|
Список | pgsql-hackers |
Hi, On 2021-05-21 18:18:54 -0400, Tom Lane wrote: > 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. I found the LLVM commit to blame (c8fc5e3ba942057d6c4cdcd1faeae69a28e7b671). Contacting the author and reading the change to see if I can spit the issue myself. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: