All tested version of Intel OneAPI's `icx` compiler segfault in the `gl_cv_func_working_error` test added in "error: Work around an Android problem." (2886cca8398f4c5a4d68368a19c0e6d0ff97c739).
For details see the issue upstream https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/All-versions-of-icx-miscompile-error-0-resulting-in-segfaults/m-p/1744208 or this link to compiler explorer: https://godbolt.org/z/Exfsc8j8Y. The issue is that `icx` treats `error (0, 0, "foo");` as noreturn, but `error(0, ...)` should return, and lacks xor eax, eax add rsp, 8 ret A user reports that "[c]onfigure hangs forever, eating RAM until OOM kill." For me, I'm getting that repeatedly prints "foo" until it segfaults: ``` foo foo foo Segmentation fault (core dumped) ``` I think it's sensible not to run the compiled executable, just like in the cross compile case. Best, Harmen Stoppels
