public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/23380] [mingw32] cpu_time intrinsic malfunction Date: Sat, 13 Aug 2005 21:55:00 -0000 [thread overview] Message-ID: <20050813215529.25854.qmail@sourceware.org> (raw) In-Reply-To: <20050813214828.23380.edunlop@utvinternet.ie> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-13 21:55 ------- This is a mingw32 specific issue. The implemention for mingw32 is not complete. intrinsics/cpu_time.c is where it is implemented, we only check for HAVE_GETRUSAGE and HAVE_TIMES. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|fortran |libfortran Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2005-08-13 21:55:29 date| | Summary|cpu_time intrinsic |[mingw32] cpu_time intrinsic |malfunction |malfunction http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23380
next prev parent reply other threads:[~2005-08-13 21:55 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-13 21:48 [Bug fortran/23380] New: " edunlop at utvinternet dot ie 2005-08-13 21:55 ` pinskia at gcc dot gnu dot org [this message] 2005-08-14 1:34 ` [Bug libfortran/23380] [mingw32] " 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=20050813215529.25854.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).