public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38199] missed optimization, regression: I/O performance
Date: Thu, 20 Nov 2008 14:06:00 -0000 [thread overview]
Message-ID: <20081120140455.29205.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38199-9562@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from jb at gcc dot gnu dot org 2008-11-20 14:04 -------
I'm looking at I/O performance as part of PR 25561 (see also PR 37754, perhaps
this is a dup?), but my changes are invasive enough that they are 4.5 material.
Thanks for the report.
--
jb at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jb at gcc dot gnu dot org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2008-11-20 14:04:55
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38199
next prev parent reply other threads:[~2008-11-20 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 13:57 [Bug fortran/38199] New: " manfred99 at gmx dot ch
2008-11-20 14:06 ` jb at gcc dot gnu dot org [this message]
2008-11-20 15:00 ` [Bug fortran/38199] " manfred99 at gmx dot ch
2008-11-20 15:58 ` [Bug fortran/38199] [4.4 regression] " burnus at gcc dot gnu dot org
2008-11-20 16:11 ` manfred99 at gmx dot ch
2008-11-21 4:15 ` jvdelisle at gcc dot gnu dot org
2008-11-21 13:55 ` [Bug fortran/38199] missed optimization: " pault at gcc dot gnu dot org
2008-11-22 5:35 ` jvdelisle at gcc dot gnu dot org
2010-02-13 6:39 ` jvdelisle at gcc dot gnu dot org
2010-02-13 6:40 ` jvdelisle at gcc dot gnu dot org
2010-02-21 15:59 ` jvdelisle 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=20081120140455.29205.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: 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).