public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18048] [4.0 Regression] mgrid loop performance regression with ivopts
Date: Wed, 27 Oct 2004 20:27:00 -0000 [thread overview]
Message-ID: <20041027202732.18309.qmail@sourceware.org> (raw)
In-Reply-To: <20041018192236.18048.dje@gcc.gnu.org>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-10-27 20:27 -------
Subject: Bug 18048
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: rakdver@gcc.gnu.org 2004-10-27 20:27:21
Modified files:
gcc : ChangeLog fold-const.c tree-ssa-loop-ivopts.c
tree-ssa-loop-niter.c tree.c tree.h
Log message:
PR tree-optimization/18048
* fold-const.c (try_move_mult_to_index): New function.
(fold): Use try_move_mult_to_index.
* tree-ssa-loop-ivopts.c (try_add_cand_for): Prefer common candidates.
* tree-ssa-loop-niter.c (number_of_iterations_cond): Produce
an all-ones unsigned constant without extra bits.
* tree.c (build_low_bits_mask): New function.
* tree.h (build_low_bits_mask): Declare.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.6052&r2=2.6053
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fold-const.c.diff?cvsroot=gcc&r1=1.468&r2=1.469
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-ssa-loop-ivopts.c.diff?cvsroot=gcc&r1=2.20&r2=2.21
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-ssa-loop-niter.c.diff?cvsroot=gcc&r1=2.13&r2=2.14
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree.c.diff?cvsroot=gcc&r1=1.440&r2=1.441
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree.h.diff?cvsroot=gcc&r1=1.640&r2=1.641
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18048
next prev parent reply other threads:[~2004-10-27 20:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 19:22 [Bug tree-optimization/18048] New: " dje at gcc dot gnu dot org
2004-10-18 19:24 ` [Bug tree-optimization/18048] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-10-19 16:46 ` matz at suse dot de
2004-10-22 17:35 ` pinskia at gcc dot gnu dot org
2004-10-22 18:39 ` dje at gcc dot gnu dot org
2004-10-22 21:16 ` rakdver at atrey dot karlin dot mff dot cuni dot cz
2004-10-27 20:27 ` cvs-commit at gcc dot gnu dot org [this message]
2004-11-27 21:17 ` neroden at gcc dot gnu dot org
2004-12-26 14:50 ` pinskia at gcc dot gnu dot org
2004-12-26 14:58 ` pinskia at gcc dot gnu dot org
2005-01-06 23:02 ` pinskia at gcc dot gnu dot org
2005-01-22 16:49 ` dberlin at gcc dot gnu dot org
2005-01-22 17:54 ` pinskia at gcc dot gnu dot org
2005-01-22 21:37 ` pinskia at gcc dot gnu dot org
2005-01-23 0:24 ` steven at gcc dot gnu dot org
2005-01-23 13:17 ` steven at gcc dot gnu dot org
2005-01-30 4:37 ` [Bug tree-optimization/18048] [4.0 Regression] mgrid loop performance regression with ivopts (register pressure) pinskia at gcc dot gnu dot org
2005-02-10 22:59 ` pinskia at gcc dot gnu dot org
2005-02-11 0:37 ` pinskia at gcc dot gnu dot org
2005-02-14 15:48 ` steven at gcc dot gnu dot org
2005-02-14 20:06 ` pinskia at gcc dot gnu dot org
2005-02-14 20:22 ` dje at gcc dot gnu dot org
2005-04-21 4:58 ` [Bug tree-optimization/18048] [4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-07-08 1:34 ` mmitchel at gcc dot gnu dot org
2005-09-27 15:57 ` mmitchel 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=20041027202732.18309.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).