public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dann at godzilla dot ics dot uci dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/14736] [tree-ssa] code quality regression
Date: Wed, 02 Jun 2004 17:38:00 -0000 [thread overview]
Message-ID: <20040602173828.10460.qmail@sourceware.org> (raw)
In-Reply-To: <20040325231958.14736.dann@godzilla.ics.uci.edu>
------- Additional Comments From dann at godzilla dot ics dot uci dot edu 2004-06-02 17:38 -------
(In reply to comment #7)
> Much newer and simpler patch:
<http://gcc.gnu.org/ml/gcc-patches/2004-06/msg00087.html>.
Great! Thanks for taking care of this!
Could you also post some before and after numbers? They should be very interesting.
Like the number of lines in the dump files, or the number of temp variables
created.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14736
next prev parent reply other threads:[~2004-06-02 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 23:20 [Bug optimization/14736] New: " dann at godzilla dot ics dot uci dot edu
2004-03-25 23:34 ` [Bug optimization/14736] " pinskia at gcc dot gnu dot org
2004-04-06 19:15 ` pinskia at gcc dot gnu dot org
2004-05-17 0:14 ` [Bug tree-optimization/14736] " pinskia at gcc dot gnu dot org
2004-05-17 13:41 ` pinskia at gcc dot gnu dot org
2004-06-02 4:32 ` pinskia at gcc dot gnu dot org
2004-06-02 4:33 ` pinskia at gcc dot gnu dot org
2004-06-02 4:41 ` pinskia at gcc dot gnu dot org
2004-06-02 17:38 ` dann at godzilla dot ics dot uci dot edu [this message]
2004-06-02 18:57 ` cvs-commit at gcc dot gnu dot org
2004-06-02 19:00 ` pinskia at gcc dot gnu dot org
2004-06-02 19:58 ` pinskia 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=20040602173828.10460.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).