Hi, On Mon, Sep 25, 2023 at 01:48:01PM +0300, Stephan Bergmann <sbergman@xxxxxxxxxx> wrote: > Was that maybe an intermittent Clang bug? It apparently doesn't hit the > Jenkins Clang builds, and I don't see it with trunk Clang 18 either, but > have dim memories that there was some issue with too-eager evaluation > causing something like this at some point. Do you have a way to check with > another Clang version, to substantiate that assumption? Yes, I can confirm downgrading to clang-12 would work around the problem. On Mon, Sep 25, 2023 at 12:57:56PM +0100, Caolán McNamara <caolan.mcnamara@xxxxxxxxxxxxx> wrote: > On Mon, 2023-09-25 at 13:48 +0300, Stephan Bergmann wrote: > > Was that maybe an intermittent Clang bug? It apparently doesn't hit > > the Jenkins Clang builds, and I don't see it with trunk Clang 18 > > either > > I'm seeing it in oss-fuzz too FWIW, like > https://oss-fuzz-build-logs.storage.googleapis.com/log-d8e659e6-8b3e-45b0-9676-ceb57d8152f4.txt I see this got fixed with core.git commit 7f75bfd0f6b1bf4debb69e96c114e453c62685f8 (Don't enable the requires clause for Clang 15, 2023-09-25), and that also fixed my original setup. Thanks, Miklos