rorth wrote: > > At least in the short term. ISTM that `clang++` may need to do something > > along the lines of Bug 33767 (resp. the underlying GCC bug/patch), > > otherwise users are in for a nasty surprise. > > Agreed; long-term we need a better solution. Hopefully someone maintaining > Solaris support can step in and help there, because this is quite surprising > behavior.
The cleaned-up hack is in the final rounds of testing. Wlll create a PR once that's done. There's no real Solaris maintainer AFAIK: while I do run the buildbots and try to keep the port in shape as time allows, I can only do so much. The Solaris GCC maintainership takes enough of my time and splitting it would only be to the detriment of both projects. TBH, I wouldn't even know where to look: I've mostly dealt with `compiler-rt` and driver issues so far. https://github.com/llvm/llvm-project/pull/99075 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
