kikairoya wrote: > To confirm my understanding, the test strategy here is checking that > everything behaves just like linux-itanium, except for scenarios with > optimisations which will cause the vtable to be external, and in those cases > vtable-debug-locations shouldn't be emitted. (Am I right?)
Yes, exactly. Repeating everything for MinGW looks redundant a bit, but I believe it's important to catch any unintentional changes early on. https://github.com/llvm/llvm-project/pull/158450 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits