3 ms·
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 gar
by dooglius 1y ago
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
- bombcar 1y agoThis would result in many more disasters as system GCC and kernel GCC would quickly be out of sync causing all sorts of "unexpected fun".
- dooglius 1y agoWhy 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.
- ndesaulniers 1y agoYou'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.
- dooglius 1y agoAh that's interesting, thanks