GCC15 changes the signature of the `__tsan_func_exit` builtin function from `void(void *)` to `void(void)` in the following commit <https://github.com/gcc-mirror/gcc/commit/07565115371e#diff-1e5bf766c4c8924f68cb79315944f820eabd44bf881f2db7e746af4df86cd0a8R250> Attaching the godbolt <https://godbolt.org/z/x3fda57r5> link showcasing the warning generated Currently I am working with a codebase which explicitly calls `__tsan_func_exit(NULL)` in certain places and am curious as to whether backwards compatibility of the builtin function signatures is a goal? There is also a function declaration of `__tsan_func_exit` in tsan_interface.h <https://github.com/gcc-mirror/gcc/blob/28219f7f99a80519d1c6ab5e5dc83b4c7f8d7251/libsanitizer/tsan/tsan_interface.h#L86>, which seems to have always been `void(void)`, Is this different from the builtin? Are the contents of this header not exposed to users of the compiler? -- Hari Hara Naveen
