public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at tat dot physik dot uni-tuebingen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/11707] [3.4 Regression] [new unroller] constants not propagated in unrolled loop iterations with a conditional
Date: Mon, 29 Sep 2003 14:39:00 -0000 [thread overview]
Message-ID: <20030929141417.28706.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030729133436.11707.rguenth@tat.physik.uni-tuebingen.de>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11707
------- Additional Comments From rguenth at tat dot physik dot uni-tuebingen dot de 2003-09-29 14:14 -------
Subject: Re: [3.4 Regression] [new unroller] constants
not propagated in unrolled loop iterations with a conditional
On 29 Sep 2003, rakdver at gcc dot gnu dot org wrote:
> Anyway, the attached patch fixes the problem. I believe moving jump bypassing
> after unroller should not harm anything.
This may be the fix for the 3.4 regression. What about the 3.3 regression?
I.e. the unneccessary imull produced on x86? This is a regression to
2.95.3 as noted in comment #3.
Maybe someone could look what is preventing constant folding from being
done here. Roger?
Thanks,
Richard.
--
Richard Guenther <richard dot guenther at uni-tuebingen dot de>
WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/
next prev parent reply other threads:[~2003-09-29 14:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 13:34 [Bug optimization/11707] New: " rguenth at tat dot physik dot uni-tuebingen dot de
2003-07-29 13:40 ` [Bug optimization/11707] " pinskia at physics dot uc dot edu
2003-07-29 13:45 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-07-29 14:07 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-07-29 14:13 ` [Bug optimization/11707] [3.4 Regression] [new unroller] " pinskia at physics dot uc dot edu
2003-09-29 13:54 ` rakdver at gcc dot gnu dot org
2003-09-29 14:14 ` rakdver at gcc dot gnu dot org
2003-09-29 14:39 ` rguenth at tat dot physik dot uni-tuebingen dot de [this message]
2003-09-29 16:48 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-12-05 3:33 ` pinskia at gcc dot gnu dot org
2003-12-05 21:47 ` rakdver at atrey dot karlin dot mff dot cuni dot cz
2004-01-04 8:54 ` pinskia at gcc dot gnu dot org
2004-03-09 23:27 ` [Bug optimization/11707] [3.4/3.5 " mmitchel at gcc dot gnu dot org
2004-03-09 23:28 ` mmitchel at gcc dot gnu dot org
2004-03-21 18:24 ` steven at gcc dot gnu dot org
2004-06-18 23:41 ` [Bug rtl-optimization/11707] " mmitchel at gcc dot gnu dot org
2004-08-10 1:38 ` pinskia at gcc dot gnu dot org
2004-08-12 7:33 ` steven at gcc dot gnu dot org
2004-08-29 19:02 ` [Bug rtl-optimization/11707] [3.4 " mmitchel at gcc dot gnu dot org
2004-10-30 19:34 ` mmitchel at gcc dot gnu dot org
2004-11-01 0:45 ` mmitchel at gcc dot gnu dot org
2005-01-12 11:06 ` rguenth at tat dot physik dot uni-tuebingen dot de
2005-02-10 18:35 ` rguenth at gcc dot gnu dot org
2005-02-10 18:36 ` steven at gcc dot gnu dot org
2005-05-19 17:24 ` mmitchel at gcc dot gnu dot org
2005-08-22 12:49 ` 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=20030929141417.28706.qmail@sources.redhat.com \
--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).