DavidSpickett wrote:

> since it is neither a recent regression nor a fix that has broad impact (from 
> what I can tell)

In that case I'll abandon this and it'll be fixed in 22. The impact is part of 
a variable being printed incorrectly, but it does emit an error so users know 
something is not right.

https://github.com/llvm/llvm-project/pull/170854
_______________________________________________
llvm-branch-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

Reply via email to