https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70128
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Marcin Juszkiewicz from comment #9) > Nicolas Pitre (author of kernel patch) wrote to me: > As you can see, the value 5 is dropped. > > Let's hope gcc will be fixed. This assumes this is a gcc bug, which is not something that has been agreed on. The code is not valid C, and the only question we are discussing is whether we want to accept it as an extension with -fno-strict-aliasing, or not. Because at least GCC 4.6 to current trunk behave this way, I strongly believe the kernel needs to be adjusted, because even if we decide now we want to accept it as extension, there are 5 major releases of gcc that behave this way.
