public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/23380] [4.0 only] [mingw32] cpu_time intrinsic malfunction Date: Sat, 24 Sep 2005 08:41:00 -0000 [thread overview] Message-ID: <20050924084059.23504.qmail@sourceware.org> (raw) In-Reply-To: <20050813214828.23380.edunlop@utvinternet.ie> -- What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |fxcoudert at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Known to fail| |4.0.2 Known to work| |4.1.0 Last reconfirmed|2005-09-06 17:21:59 |2005-09-24 08:40:58 date| | Summary|[mingw32] cpu_time intrinsic|[4.0 only] [mingw32] |malfunction |cpu_time intrinsic | |malfunction Target Milestone|--- |4.1.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23380
next prev parent reply other threads:[~2005-09-24 8:41 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 ` [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 ` fxcoudert at gcc dot gnu dot org [this message] 2005-09-29 12:29 ` [Bug libfortran/23380] [4.0 only] " 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=20050924084059.23504.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).