Re:Some __nonstring__ Turbulence
by dooglius on Friday April 25, 2025 @06:09AM
(#43792011)
People are usually going to go through `make`, I don't see a reason that couldn't be instrumented to (by default) acquire an upstream GCC vs whatever forked garbage ends up in $PATH
[ Parent
| on HN ]
This would result in many more disasters as system GCC and kernel GCC would quickly be out of sync causing all sorts of "unexpected fun".
Why would it go wrong, the ABI is stable and independent of compiler? You would hit issues with C++ but not C. I have certainly built kernels using different versions of GCC than what /lib stuff is compiled with, without issue.
Re:Some __nonstring__ Turbulence
by ndesaulniers on Friday April 25, 2025 @12:05PM
(#43795163)
You'd think that, but in effect kconfig/kbuild has many cases where they say "if the compiler supports flag X, use it" where X implies an ABI break. Per task stack protectors comes to mind.