public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot 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: Mon, 14 Dec 2009 20:46:00 -0000	[thread overview]
Message-ID: <20091214204600.7910.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30617-12313@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2009-12-14 20:46 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-27 19:47 [Bug fortran/30617] New: recursive I/O hangs under OSX 10.3 dominiq at lps dot ens dot fr
2007-01-27 21:31 ` [Bug fortran/30617] " kargl at gcc dot gnu dot org
2007-01-27 21:38 ` kargl at gcc dot gnu dot org
2007-01-27 21:43 ` dominiq at lps dot ens dot fr
2007-01-27 21:48 ` [Bug libfortran/30617] " pinskia at gcc dot gnu dot org
2007-01-27 21:51 ` jvdelisle at gcc dot gnu dot org
2007-01-27 22:01 ` dominiq at lps dot ens dot fr
2007-01-27 23:34 ` kargl at gcc dot gnu dot org
2007-01-29 13:46 ` dir at lanl dot gov
2007-01-29 14:13 ` dominiq at lps dot ens dot fr
2007-02-05 22:15 ` fxcoudert at gcc dot gnu dot org
2007-02-06  3:04 ` jvdelisle at gcc dot gnu dot org
2007-02-07  9:10 ` brooks at gcc dot gnu dot org
2007-02-07  9:24 ` dominiq at lps dot ens dot fr
2007-02-07 19:55 ` [Bug libfortran/30617] recursive I/O hangs under OSX dominiq at lps dot ens dot fr
2007-02-08  3:12 ` jvdelisle at gcc dot gnu dot org
2007-02-08  8:46 ` dominiq at lps dot ens dot fr
2007-02-08  9:36 ` jakub at gcc dot gnu dot org
2007-02-08 10:03 ` dominiq at lps dot ens dot fr
2007-02-08 12:07 ` dominiq at lps dot ens dot fr
2007-02-08 16:18 ` kargl at gcc dot gnu dot org
2007-02-11 20:59 ` pault at gcc dot gnu dot org
2007-02-12  7:37 ` dominiq at lps dot ens dot fr
2007-02-17 17:17 ` pault at gcc dot gnu dot org
2007-03-03 13:31 ` fxcoudert at gcc dot gnu dot org
2007-03-03 20:56 ` burnus at gcc dot gnu dot org
2007-03-03 21:46 ` dominiq at lps dot ens dot fr
2007-04-24 10:59 ` jakub at gcc dot gnu dot org
2007-04-24 12:04 ` dominiq at lps dot ens dot fr
2007-04-24 14:46 ` pinskia at gcc dot gnu dot org
2007-04-24 14:59 ` dominiq at lps dot ens dot fr
2008-07-11 22:19 ` dominiq at lps dot ens dot fr
2008-07-11 22:22 ` 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 [this message]
2009-12-14 20:52 ` dominiq at lps dot ens dot fr
     [not found] <bug-30617-4@http.gcc.gnu.org/bugzilla/>
2013-02-27 18:19 ` dominiq at lps dot ens.fr
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

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=20091214204600.7910.qmail@sourceware.org \
    --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: link
Be 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).