[Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O

2020-11-28 Thread dominiq at lps dot ens.fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617 Dominique d'Humieres changed: What|Removed |Added CC||anthony.debeus at gmail dot com -

[Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O

2015-08-26 Thread fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617 Francois-Xavier Coudert changed: What|Removed |Added Last reconfirmed|2007-03-03 13:31:17 |2015-8-26 CC|

[Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O

2014-10-16 Thread sidio47 at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617 Cyrus changed: What|Removed |Added CC||sidio47 at hotmail dot com --- Comment #40 from

[Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O

2014-10-16 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617 --- Comment #39 from Jakub Jelinek --- (In reply to Dominique d'Humieres from comment #29) > > It is hanging on undefined, I think there is a difference here, a big > > difference. > > What is the difference for you? > > Just as a side note, th

[Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O

2014-08-02 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617 Dominique d'Humieres changed: What|Removed |Added CC||jannis at teunissen dot net --- C

[Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O

2014-05-20 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617 Dominique d'Humieres changed: What|Removed |Added CC||peter.machon at arcor dot de ---

[Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O

2013-02-27 Thread dominiq at lps dot ens.fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617 Dominique d'Humieres changed: What|Removed |Added CC||stefano.borini at ferrara

[Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O

2009-12-14 Thread dominiq at lps dot ens dot fr
--- Comment #35 from dominiq at lps dot ens dot fr 2009-12-14 20:51 --- Wrong pr. Sorry for the noise. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617

[Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O

2009-12-14 Thread dominiq at lps dot ens dot fr
--- Comment #34 from dominiq at lps dot ens dot fr 2009-12-14 20:45 --- Created an attachment (id=19297) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19297&action=view) assembly generated without -frename-registers -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617

[Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O

2009-12-14 Thread dominiq at lps dot ens dot fr
--- Comment #33 from dominiq at lps dot ens dot fr 2009-12-14 20:43 --- Created an attachment (id=19296) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19296&action=view) assembly generated with -frename-registers -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617

[Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O

2009-05-07 Thread dominiq at lps dot ens dot fr
--- Comment #32 from dominiq at lps dot ens dot fr 2009-05-07 22:00 --- Presently invalid recursive I/Os are accepted by gfortran without any diagnostic at run time. It could be helpful to implement such a diagnostic with something such as -fcheck=recursive_IO. Note that xlf gives a run