[compiler-rt] [asan,test] Disable _FORTIFY_SOURCE test incompatible with glibc 2.40 (PR #101566)

[Fangrui Song via llvm-commits]

MaskRay wrote:

> LGTM to me as well, but I wonder how hard would to make sanitizer work properly with forfity calls (maybe just bypass them to internal fortify implementations). Distros are now setting the fortify cflags as default for their toolchain packages, and it would be good usability if users do not need to disable fortify to enable sanitizers.

Thanks for the comment. To work with fortify calls in an uninstrumented prebuilt DSO, interceptors would be needed.
To work with forced `-D_FORTIFY_SOURCE=[2|3]`, perhaps in some cases instead of more interceptors, the C library headers or `__builtin_*` function implementation can do something.

In any case, there is substantial exploration area that the release/19.x releases will be ready for. We can disable this test first.

https://github.com/llvm/llvm-project/pull/101566