[Bug middle-end/64099] [5/6 Regression] ~15% runtime increase for fatigue.f90.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64099 Richard Biener changed: What|Removed |Added Target Milestone|5.3 |5.4 --- Comment #17 from Richard Biener --- GCC 5.3 is being released, adjusting target milestone.
[Bug middle-end/64099] [5/6 Regression] ~15% runtime increase for fatigue.f90.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64099 Richard Biener rguenth at gcc dot gnu.org changed: What|Removed |Added Target Milestone|5.2 |5.3 --- Comment #16 from Richard Biener rguenth at gcc dot gnu.org --- GCC 5.2 is being released, adjusting target milestone to 5.3.
[Bug middle-end/64099] [5/6 Regression] ~15% runtime increase for fatigue.f90.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64099 Jakub Jelinek jakub at gcc dot gnu.org changed: What|Removed |Added Target Milestone|5.0 |5.2 --- Comment #15 from Jakub Jelinek jakub at gcc dot gnu.org --- GCC 5.1 has been released.
[Bug middle-end/64099] [5/6 Regression] ~15% runtime increase for fatigue.f90.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64099 --- Comment #14 from Dominique d'Humieres dominiq at lps dot ens.fr --- Created attachment 35320 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=35320action=edit Reduced version with most I/Os removed and generalized_hookes_law inlined manually. The subroutine perdida is fully inlined when this test is compiled with -Ofast.
[Bug middle-end/64099] [5/6 Regression] ~15% runtime increase for fatigue.f90.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64099 --- Comment #12 from Dominique d'Humieres dominiq at lps dot ens.fr --- The timing increase disappears if the code is compiled with -fno-tree-dominator-opts.
[Bug middle-end/64099] [5/6 Regression] ~15% runtime increase for fatigue.f90.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64099 --- Comment #13 from Dominique d'Humieres dominiq at lps dot ens.fr --- Created attachment 35319 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=35319action=edit Reduced version with most I/Os removed. Run time can be tuned by changing the value of number_of_sample_points. With the current value (50) run time is ~6s when the test is compiled with -Ofast -fwhole-program -fno-tree-dominator-opts and ~7s without -fno-tree-dominator-opts (2.8Ghz Core i7).