this should be fixed now, for clang-11 at least, courtesy of @landonf finding the relevant upstream commit in the llvm tree and backporting it to clang-11.
Ken
this should be fixed now, for clang-11 at least, courtesy of @landonf finding the relevant upstream commit in the llvm tree and backporting it to clang-11.
Ken