public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "edunlop at utvinternet dot ie" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/23380] New: cpu_time intrinsic malfunction Date: Sat, 13 Aug 2005 21:48:00 -0000 [thread overview] Message-ID: <20050813214828.23380.edunlop@utvinternet.ie> (raw) The gfortran intrinsic function cpu_time(x) does not measure cpu time - it always produces 0.0 (zero) as the result. I am using "Native Windows build: download the latest installer (2005-08-06)" from http://gcc.gnu.org/wiki/GFortranBinaries, and am running under Windows XP Professional. -- Summary: cpu_time intrinsic malfunction Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: edunlop at utvinternet dot ie CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23380
next reply other threads:[~2005-08-13 21:48 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-13 21:48 edunlop at utvinternet dot ie [this message] 2005-08-13 21:55 ` [Bug libfortran/23380] [mingw32] " pinskia at gcc dot gnu dot org 2005-08-14 1:34 ` kargl at gcc dot gnu dot org 2005-08-14 7:29 ` dannysmith at users dot sourceforge dot net 2005-08-14 9:41 ` edunlop at utvinternet dot ie 2005-08-14 16:48 ` kargl at gcc dot gnu dot org 2005-08-14 20:56 ` dannysmith at users dot sourceforge dot net 2005-09-06 17:22 ` fxcoudert at gcc dot gnu dot org 2005-09-24 8:39 ` cvs-commit at gcc dot gnu dot org 2005-09-24 8:41 ` [Bug libfortran/23380] [4.0 only] " fxcoudert at gcc dot gnu dot org 2005-09-29 12:29 ` cvs-commit at gcc dot gnu dot org 2005-09-29 12:30 ` [Bug libfortran/23380] " fxcoudert 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=20050813214828.23380.edunlop@utvinternet.ie \ --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).