public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/28484] F2003: system_clock with real-type count_rate does not compile
Date: Sat, 11 Apr 2009 21:36:00 -0000 [thread overview]
Message-ID: <20090411213557.10238.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28484-1719@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-04-11 21:35 -------
Raising this up a little since F2003 features are coming up
--
jvdelisle at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|enhancement |normal
Summary|system_clock with real-type |F2003: system_clock with
|count_rate does not compile |real-type count_rate does
| |not compile
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28484
next prev parent reply other threads:[~2009-04-11 21:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 17:09 [Bug fortran/28484] New: " tobias dot burnus at physik dot fu-berlin dot de
2006-07-25 20:22 ` [Bug fortran/28484] " kargl at gcc dot gnu dot org
2006-09-03 6:10 ` pinskia at gcc dot gnu dot org
2006-10-28 16:39 ` patchapp at dberlin dot org
2006-10-28 22:13 ` burnus at gcc dot gnu dot org
2006-11-02 16:02 ` burnus at gcc dot gnu dot org
2006-11-02 16:32 ` burnus at gcc dot gnu dot org
2007-05-22 15:16 ` burnus at gcc dot gnu dot org
2007-05-22 15:18 ` burnus at gcc dot gnu dot org
2007-05-29 20:44 ` dfranke at gcc dot gnu dot org
2007-10-26 7:32 ` jv244 at cam dot ac dot uk
2007-12-13 19:14 ` dfranke at gcc dot gnu dot org
2009-04-11 21:36 ` jvdelisle at gcc dot gnu dot org [this message]
2009-12-19 10:50 ` [Bug fortran/28484] F2003: " jb at gcc dot gnu dot org
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=20090411213557.10238.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).