public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O Date: Wed, 27 Feb 2013 18:19:00 -0000 [thread overview] Message-ID: <bug-30617-4-Ni1ENJoV0t@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-30617-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefano.borini at ferrara | |dot linux.it --- Comment #36 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2013-02-27 18:18:38 UTC --- *** Bug 51286 has been marked as a duplicate of this bug. ***
next parent reply other threads:[~2013-02-27 18:19 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-30617-4@http.gcc.gnu.org/bugzilla/> 2013-02-27 18:19 ` dominiq at lps dot ens.fr [this message] 2014-05-20 13:58 ` dominiq at lps dot ens.fr 2014-08-03 0:08 ` dominiq at lps dot ens.fr 2014-10-16 13:50 ` jakub at gcc dot gnu.org 2014-10-16 13:57 ` sidio47 at hotmail dot com 2015-08-26 17:12 ` fxcoudert at gcc dot gnu.org 2020-11-28 22:54 ` dominiq at lps dot ens.fr 2007-01-27 19:47 [Bug fortran/30617] New: recursive I/O hangs under OSX 10.3 dominiq at lps dot ens dot fr 2009-05-07 22:00 ` [Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O dominiq at lps dot ens dot fr 2009-12-14 20:43 ` dominiq at lps dot ens dot fr 2009-12-14 20:46 ` dominiq at lps dot ens dot fr 2009-12-14 20:52 ` dominiq at lps dot ens dot fr
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-30617-4-Ni1ENJoV0t@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).