public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/17088] poor fortran optimisation at -O2/3
Date: Thu, 06 Jan 2005 21:30:00 -0000 [thread overview]
Message-ID: <20050106213039.25826.qmail@sourceware.org> (raw)
In-Reply-To: <20040818204713.17088.jv244@cam.ac.uk>
------- Additional Comments From jv244 at cam dot ac dot uk 2005-01-06 21:30 -------
(In reply to comment #8)
> On closer inspection this is not a new-ra bug, sorry Joost.
> Can you see how the numbers look for you today? Don't use new-ra, it is
> known to be very, very broken.
timings for -O1 and -O2 are still unchanged for a recent version of gfortran,
i.e. -O2 is half the speed of -O1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17088
next prev parent reply other threads:[~2005-01-06 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 20:47 [Bug rtl-optimization/17088] New: poor optimisation at -O2/3 and -fnew-ra jv244 at cam dot ac dot uk
2004-08-18 20:48 ` [Bug rtl-optimization/17088] " jv244 at cam dot ac dot uk
2004-08-19 19:00 ` [Bug rtl-optimization/17088] [new-ra] " pinskia at gcc dot gnu dot org
2004-08-19 19:01 ` pinskia at gcc dot gnu dot org
2004-08-19 19:27 ` jv244 at cam dot ac dot uk
2004-08-19 19:29 ` [Bug rtl-optimization/17088] " pinskia at gcc dot gnu dot org
2005-01-03 12:09 ` [Bug rtl-optimization/17088] [new-ra] " steven at gcc dot gnu dot org
2005-01-03 12:09 ` steven at gcc dot gnu dot org
2005-01-03 12:20 ` [Bug rtl-optimization/17088] poor fortran optimisation at -O2/3 steven at gcc dot gnu dot org
2005-01-06 21:30 ` jv244 at cam dot ac dot uk [this message]
2005-01-06 21:39 ` pinskia at gcc dot gnu dot org
2005-01-17 15:33 ` pinskia at gcc dot gnu dot org
2005-04-07 7:25 ` pinskia at gcc dot gnu dot org
[not found] <bug-17088-6642@http.gcc.gnu.org/bugzilla/>
2006-05-02 5:01 ` jvdelisle at gcc dot gnu dot org
2007-07-03 18:15 ` jv244 at cam dot ac dot uk
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=20050106213039.25826.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).