philnik777 wrote: > > At least the libc++abi checks are completely unnecessary. We only support a > > single GCC version and that has `__has_feature`. I'm not quite clear what > > the libunwind requirements are, but I'm pretty sure the docs are out of > > date on that. > > Actually, I just looked at the original report and it reports a failure in > gcc13.x, but gcc is apparently up to 15.x - is 13.x actually supported? (I > had assumed it was current gcc being reported)
libc++abi requires GCC 15. As I said, it's not really clear for libunwind for me. IMO we should just require the latest GCC there as well as that's the only tested version AFAIK, but that's not something we should do in a random patch. > Hmm, the unwind docs claim gcc 4.7 or clang 3.5 which seems optimistic? Yeah, exactly. I would be _very_ surprised if that was actually true. https://github.com/llvm/llvm-project/pull/164535 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
