http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59612
--- Comment #7 from janus at gcc dot gnu.org ---
(In reply to janus from comment #2)
> Does -fdump-fortran-optimized actually do anything?
The reason why I did not get any output from it is of course that it is only in
effect if -ffrontend-optimiz
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59612
--- Comment #6 from janus at gcc dot gnu.org ---
The patches of comment 1 and 2 have been applied in r206237, so that the
original problem is fixed by now.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59612
--- Comment #5 from janus at gcc dot gnu.org ---
Author: janus
Date: Sun Dec 29 17:20:50 2013
New Revision: 206237
URL: http://gcc.gnu.org/viewcvs?rev=206237&root=gcc&view=rev
Log:
2013-12-29 Janus Weil
PR fortran/59612
* dump-parse-tr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59612
--- Comment #4 from janus at gcc dot gnu.org ---
(In reply to janus from comment #3)
> Maybe it would make sense to run the testsuite with -fdump-fortran-original,
> in order to check for further problems:
Does not seem to yield any failures here
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59612
--- Comment #3 from janus at gcc dot gnu.org ---
Maybe it would make sense to run the testsuite with -fdump-fortran-original, in
order to check for further problems:
Index: gcc/testsuite/gfortran.dg/dg.exp
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59612
--- Comment #2 from janus at gcc dot gnu.org ---
Note that there are two small errors in the related documentation:
Index: gcc/fortran/invoke.texi
===
--- gcc/fortran/invoke.texi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59612
janus at gcc dot gnu.org changed:
What|Removed |Added
Keywords||ice-on-valid-code
S
