Open StephanTLavavej opened 10 months ago
This was encountered as https://groups.google.com/g/isl-development/c/ShnQcW_35ZQ and discussed on the GCC mailing list in Aug 2023 (mail 1, mail 2, mail 3) but I don't know if anyone's working on it, and I don't see anything filed in GCC Bugzilla.
Archlinux can use isl 0.26 with gcc 13.2.1 and without patches.
Is it using an in-tree build with a full bootstrap? That seems to be the important factor here.
Looking at https://gitlab.archlinux.org/archlinux/packaging/packages/gcc/-/blob/main/PKGBUILD?ref_type=heads , it appears to depend on a previously-built libisl, which explains why it isn't affected by this bug.
When re-enabling the GCC bootstrap, the following set of versions fails:
The bootstrap succeeds if I keep isl-0.24, so isl-0.26 specifically appears to be the problem.
The error is:
I looked into this, and at least part of the problem appears to be that
g++ -std=c++11
is being used, despite the code needing C++17. Part of the autoconf machinery seemed to be saying that C++17 is "optional" instead of "mandatory" but I don't really know what the root cause is, or how to solve this.I suspect that this is not specific to mingw-w64 at all.