public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "e-dunlop at versanet dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/35355] [4.3/4.4 regression] CPU_TIME gives wrong values on mingw Date: Sun, 02 Mar 2008 11:00:00 -0000 [thread overview] Message-ID: <20080302110006.25596.qmail@sourceware.org> (raw) In-Reply-To: <bug-35355-11167@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from e-dunlop at versanet dot de 2008-03-02 11:00 ------- Subject: Fw: Bug libfortran/35355 Many thanks for your input into the repair of my reported bug. Your work is really appreciated - and the process is so much better than (commercial) Intel. Best wishes, Edmund Dunlop. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35355
next prev parent reply other threads:[~2008-03-02 11:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-24 22:54 [Bug fortran/35355] New: Result of call cpu_time(x) can decrease or give non credible values with repeated calls edunlop at utvinternet dot ie 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 [this message] 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=20080302110006.25596.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: 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).