Re: [PATCH] libstdc++: Workaround for LLVM-61763 in ranges

2023-10-20 Thread Benjamin Brock
> I don't think this patch counts as legally significant, but if you contribute > again in future you should be aware of > https://gcc.gnu.org/contribute.html#legal and either complete the copyright > assignment paperwork, or add a DCO sign-off to the commit message. Thanks for the reminder. I

Re: [PATCH] libstdc++: Workaround for LLVM-61763 in ranges

2023-10-14 Thread Jonathan Wakely
On Sat, 14 Oct 2023, 00:33 Benjamin Brock, wrote: > This is my first time submitting a patch, so my apologies if I'm > submitting incorrectly or missing something. > Thanks for contributing! I don't think this patch counts as legally significant, but if you contribute again in future you should

[PATCH] libstdc++: Workaround for LLVM-61763 in ranges

2023-10-13 Thread Benjamin Brock
This is my first time submitting a patch, so my apologies if I'm submitting incorrectly or missing something. Clang is unable to compile parts of libstdc++'s ranges implementation due to LLVM-61763, a Clang frontend compiler bug in handling the declarations of constrained friends. The problem are