https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66348
Sebastiano Vigna <sebastiano.vigna at unimi dot it> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #14 from Sebastiano Vigna <sebastiano.vigna at unimi dot it> ---
In retrospect, and knowing what I know now, I don't understand why nobody just
suggested to compile with -fno-strict-aliasing. The cause of the problem are
ithe gcc super-strict aliasing rules. Compiling with -f-no-strict-aliasing
solved the problem.
