Would it be feasible to add TSan, UBSan, and ASan support?

[clin1234]

[Psychlist1972]

Presumably this is for the SDK Runtime?

Note for future consideration as most folks here aren't using clang/llvm toolchains: these are clang-specific sanitization tools:

• TSan https://clang.llvm.org/docs/ThreadSanitizer.html
• ASan https://clang.llvm.org/docs/AddressSanitizer.html
• UBSan https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html

The SDK code is relatively simple, but if we move to clang at any point, it would be good to consider these. The in-box components get compiled by the Windows internal toolchain, and do not support clang/llvm at this point, so there's no obvious advantage to adding this support there.

[clin1234]

I mean for MSVC

[Psychlist1972]

I mean for MSVC

I'll need to ask around, but as far as I know, it supports only classic Arm64, not Arm64EC or Arm64X, and there may still be incompatibilities with WinRT.

Can you explain your need for the sanitizers? Is this something you're relying on in a shipping product?

[clin1234]

I mean for MSVC

I'll need to ask around, but as far as I know, it supports only classic Arm64, not Arm64EC or Arm64X, and there may still be incompatibilities with WinRT.

Can you explain your need for the sanitizers? Is this something you're relying on in a shipping product?

More to ensure code correctness, especially when writing device drivers. Does this project target UMDF?