I have an odd question. Do the kernel dev's actually go through and install that version (5.1) of GCC and use as their daily driver? As an example on openSUSE, the base compiler is 7.5 so they would have to seriously go out of their way to install such an old compiler.
Linux Kernel Moving Ahead With Going From C89 To C11 Code
Collapse
X
-
Originally posted by dekernel View PostI have an odd question. Do the kernel dev's actually go through and install that version (5.1) of GCC and use as their daily driver? As an example on openSUSE, the base compiler is 7.5 so they would have to seriously go out of their way to install such an old compiler.
Comment
-
-
I think it's a very nice move to update to a newer standard and hope this could also help new maintainers to be comfortable to contribute.
And I also aware that I'm commenting on Phoronix forum, so I expect to see someone coming here and starting a fuss about "how this change is bad because I don't like changes" like unfortunately I do with some other tech here. But I hope I'm wrong on the latter
Comment
-
-
Originally posted by furtadopires View PostI think it's a very nice move to update to a newer standard and hope this could also help new maintainers to be comfortable to contribute.
And I also aware that I'm commenting on Phoronix forum, so I expect to see someone coming here and starting a fuss about "how this change is bad because I don't like changes" like unfortunately I do with some other tech here. But I hope I'm wrong on the latter
Comment
-
-
Originally posted by dekernel View PostI have an odd question. Do the kernel dev's actually go through and install that version (5.1) of GCC and use as their daily driver? As an example on openSUSE, the base compiler is 7.5 so they would have to seriously go out of their way to install such an old compiler.
Comment
-
-
Originally posted by kozman View PostSomeone enlighted us on what's better in C11 than C89 besides just the improved commenting format.
Comment
-
-
Considering how annoyed Linus is because of the bad shape the C standard is in, maybe we'll see an at least partial R...-based rewrite sooner than expected? At least I expect some changes in the near future.
So "undefined" behavior means that changes to code that isn't even near the code in question can change what the code generation for that code is.
And the compiler may not even report it.
That is a complete disaster.
It's a disaster from a security standpoint, it's a disaster from a maintenance standpoint, it's just *bad*.
Comment
-
-
Originally posted by kozman View PostI'd also hazard a guess that even with C11 one can pass a flag or switch to tell the C11 compiler to force-use the C89 standard? Someone enlighted us on what's better in C11 than C89 besides just the improved commenting format. If it makes things better and all benefit, then it's good no?
Comment
-
-
Originally posted by furtadopires View PostThere are articles on other sites that wrote with more details why they're making these changes right now, but in summary the newer standard can help with security vulnerabilities and the C11 compiled code is backward compatible with C89.
Comment
-
Comment