public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33015] g77 extension: Implement support for DATA jhlf /'f'/
Date: Wed, 12 May 2010 12:27:00 -0000	[thread overview]
Message-ID: <20100512122654.2517.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33015-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from dfranke at gcc dot gnu dot org  2010-05-12 12:26 -------
*** Bug 41218 has been marked as a duplicate of this bug. ***


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33015


      parent reply	other threads:[~2010-05-12 12:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 19:45 [Bug fortran/33015] New: F66/Vendor extension: Implement support for DATA jhlf/'f'/ burnus at gcc dot gnu dot org
2007-08-07 20:14 ` [Bug fortran/33015] g77/F66/vendor extension: Implement support for DATA jhlf /'f'/ burnus at gcc dot gnu dot org
2007-08-15 11:55 ` [Bug fortran/33015] g77 " fxcoudert at gcc dot gnu dot org
2010-05-11 16:38 ` dfranke at gcc dot gnu dot org
2010-05-12  3:28 ` jvdelisle at gcc dot gnu dot org
2010-05-12 12:27 ` dfranke at gcc dot gnu dot org [this message]

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=20100512122654.2517.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).