Closed aws-nslick closed 3 months ago
Thinking about this overnight, I think I'd just remove the builtin checks entirely. While I disagree with the statements that we should just let the build fail, I agree that there's no compiler that is going to be used to compile this that doesn't have these builtins. So just removing the checks seems reasonable to me.
Thinking about this overnight, I think I'd just remove the builtin checks entirely. While I disagree with the statements that we should just let the build fail, I agree that there's no compiler that is going to be used to compile this that doesn't have these builtins. So just removing the checks seems reasonable to me.
This was my preference initially, but I spent the time debugging it to fix it, so let's just go forward with fix.
edit: I re-reviewed the case we discussed in person
CHECK_GCC_BUILTIN([__builtin_nonexistent])
at the request of eraut@ and saw
that the previous revision didn't actually address that like I thought it did,
so we're back at square one, and I've reset this branch to the initial removal
commit.
Thanks.
this was previously broken under eg: clang-19 with the following error:
stop checking it in configure, and let the compiler fail if it's going to. There is no realistic compilers on any modern system where our usage of a compiler builtin actually fails the build, but there are clearly realistic compilers where our efforts to catch this in autotools prevents the build from being successful.
also re-enable clang-19 builds in gh actions.