[Bug fortran/68649] [6/7 Regression] note: code may be misoptimized unless -fno-strict-aliasing is used
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68649 Jakub Jelinek changed: What|Removed |Added Target Milestone|6.3 |6.4 --- Comment #19 from Jakub Jelinek --- GCC 6.3 is being released, adjusting target milestone.
[Bug fortran/68649] [6/7 Regression] note: code may be misoptimized unless -fno-strict-aliasing is used
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68649 --- Comment #18 from Joost VandeVondele --- since this PR, and the related PR77278 can presumably only be fixed by changing libgfortran abi (at least if I understand Richard's suggestion for fixing this). The announced major version bump of libgfortran (https://gcc.gnu.org/ml/gcc-patches/2016-10/msg01376.html) could be a good opportunity for this change. It is the major thing holding back the use of LTO with Fortran projects, I think.
[Bug fortran/68649] [6/7 Regression] note: code may be misoptimized unless -fno-strict-aliasing is used
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68649 --- Comment #17 from Richard Biener --- GCC 6.2 is being released, adjusting target milestone.
[Bug fortran/68649] [6/7 Regression] note: code may be misoptimized unless -fno-strict-aliasing is used
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68649 Richard Biener changed: What|Removed |Added Target Milestone|6.2 |6.3 --- Comment #15 from Richard Biener --- GCC 6.2 is being released, adjusting target milestone. --- Comment #16 from Richard Biener --- GCC 6.2 is being released, adjusting target milestone.
[Bug fortran/68649] [6/7 Regression] note: code may be misoptimized unless -fno-strict-aliasing is used
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68649 Jakub Jelinek changed: What|Removed |Added Target Milestone|6.0 |6.2 --- Comment #14 from Jakub Jelinek --- GCC 6.1 has been released.
