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/35355]  New: Result of call cpu_time(x) can decrease or give non credible values with repeated calls
Date: Sun, 24 Feb 2008 22:54:00 -0000	[thread overview]
Message-ID: <bug-35355-11167@http.gcc.gnu.org/bugzilla/> (raw)

Inconsistent or odd "call cpu_time(x)" behaviour on the current release of
gfortran. I am using the 32 bit Mingw version of gfortran.

C:\>gfortran -v
Using built-in specs.
Target: i386-pc-mingw32
Configured with: ../trunk/configure --prefix=/mingw
--enable-languages=c,fortran --with-gmp=/home/FX/local --with-ld=/mingw/bin/ld
--with-as=/mingw/bin/as --disable-werror --enable-bootstrap --enable-threads
--disable-nls --build=i386-pc-mingw32 --enable-libgomp --disable-shared
Thread model: win32
gcc version 4.3.0 20080127 (experimental) [trunk revision 131883] (GCC)

The "call cpu_time(x)" operations worked perfectly under a fairly recent
previous release of gfortran (sorry, I no longer have the version info).

I have declared x as follows:-

integer,parameter :: pr=selected_real_kind(6,37)
real(kind=pr) :: x

Unfortunately my code is very lengthy - but I could send it as an example if
really necessary.

Edmund Dunlop.


-- 
           Summary: Result of call cpu_time(x) can decrease or give non
                    credible values with repeated calls
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: edunlop at utvinternet dot ie


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


             reply	other threads:[~2008-02-24 22:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24 22:54 edunlop at utvinternet dot ie [this message]
2008-02-24 22:56 ` [Bug fortran/35355] " edunlop at utvinternet dot ie
2008-03-01 16:06 ` jvdelisle at gcc dot gnu dot org
2008-03-01 16:49 ` [Bug libfortran/35355] " fxcoudert at gcc dot gnu dot org
2008-03-01 16:53 ` [Bug libfortran/35355] [4.3/4.4 regression] CPU_TIME gives wrong values on mingw fxcoudert at gcc dot gnu dot org
2008-03-01 18:03 ` jvdelisle at gcc dot gnu dot org
2008-03-01 22:11 ` jvdelisle at gcc dot gnu dot org
2008-03-01 22:16 ` jvdelisle at gcc dot gnu dot org
2008-03-02  2:21 ` jvdelisle at gcc dot gnu dot org
2008-03-02 11:00 ` e-dunlop at versanet dot de
2008-03-02 18:44 ` dfranke 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=bug-35355-11167@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: 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).