News for hackers. Stuff that matters.
Re:Torvalds: Standards need to be questioned by dragontamer on Tuesday June 05, 2018 @06:55PM (#17242828)
> He doesn't specifically mention CLang

This is from the overall discussion going on in this thread. Others have shown how union-aliasing fails to work in CLang throughout this thread:

https://news.ycombinator.com/item?id=17242457

By removing the non-standard GCC-specific union{} methodology from the code, the contributor necessarily improved portability to CLang. That's just the facts.

Re:Torvalds: Standards need to be questioned by platinumrad on Tuesday June 05, 2018 @07:59PM (#17243262)
Clang now follows GCC's behavior with regard to that specific example, which makes sense, as Clang more or less explicitly aims to correctly compile the GNU dialect of C.

I think it's reasonable (and even important) for Linus to emphasize that the kernel is coded in GNU C, not strictly standards-compliant C.

Re:Torvalds: Standards need to be questioned by favorited on Tuesday June 05, 2018 @09:36PM (#17243740)
> Clang more or less explicitly aims to correctly compile the GNU dialect of C

That was super important as the compiler was first starting out, because (A) Apple's existing code was built with GCC, so it relied on GCC flags & extensions, and (B) for it to be a viable open source compiler, it needed to build large existing codebases which were already using GCC.

However, that doesn't mean that Clang will always continue to support every thing GCC does. Whether they by design or by accident, incompatibilities will arise. Of course, projects as tightly coupled to GCC as the Linux kernel might not care.