From: Zoltan Hidvegi <hzoli@hzoli.2y.net>
To: gcc@gcc.gnu.org
Subject: Loop unroll fixes
Date: Thu, 13 Sep 2001 16:35:00 -0000 [thread overview]
Message-ID: <E15hg16-0003Dh-00@hzoli.home> (raw)
Sorry to bug you all with that again, but I wonder if the fix for PR
3384 could be applied to the 3.0 branch and the mainline (on the
mainline the doloop.c patch conflicts with Bernd Smith's change to fix
a subset of the bugs fixed by my patches that also generates a slighly
less efficient code). See PR 3384, and threads
http://gcc.gnu.org/ml/gcc-patches/2001-07/msg01080.html
http://gcc.gnu.org/ml/gcc-bugs/2001-07/msg00750.html
I think this is a bad regression from 2.95.2. -funroll-loops is a
powerful and widely used optimization. GNATS already have a high
priority assigned to this bug, please, someone look at it and either
check it in or do some alrernative fix. Bootstrapped and passed the
regressions on powerpc-ibm-aix4.3.3 and on i686-pc-linux-gnu, at least
it did some time back just before 3.0.1 was released, but there has
been no change in the files involved since than.
Thanks very much,
Zoli
next reply other threads:[~2001-09-13 16:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 16:35 Zoltan Hidvegi [this message]
2001-09-13 18:58 ` David Edelsohn
2001-09-13 23:50 ` Jim Wilson
2001-09-14 6:55 ` Daniel Berlin
2001-09-14 12:15 ` Joseph S. Myers
2001-09-14 16:45 ` Jim Wilson
2001-09-14 20:11 ` David Edelsohn
2001-09-14 22:23 ` Jim Wilson
2001-09-15 2:42 ` Bernd Schmidt
2001-09-14 21:16 ` Daniel Berlin
2001-09-14 9:41 ` David Edelsohn
2001-09-14 10:46 ` Bernd Schmidt
2001-09-14 11:47 ` David Edelsohn
2001-09-14 17:54 ` Jim Wilson
2001-09-14 18:35 ` David Edelsohn
2001-09-14 19:56 ` Jim Wilson
2001-09-15 2:56 ` Joseph S. Myers
2001-10-04 6:46 ` Franz Sirl
2001-10-04 7:40 ` Mark Mitchell
2001-10-04 20:46 ` Jim Wilson
2001-10-04 20:51 ` Mark Mitchell
2001-10-04 23:10 ` Zoltan Hidvegi
2001-10-10 0:05 ` Mark Mitchell
[not found] <Pine.LNX.4.33.0109141957550.29416-100000@host140.cambridge.redhat.com>
2001-09-14 14:36 ` David Edelsohn
[not found] <200109142021.QAA26236@makai.watson.ibm.com>
2001-09-15 8:57 ` Bernd Schmidt
2001-09-17 13:16 ` Richard Henderson
2001-09-17 14:24 ` Joe Buck
2001-09-17 15:11 ` Richard Henderson
2001-09-17 17:22 ` Mark Mitchell
2001-09-18 2:19 ` Joseph S. Myers
2001-09-18 4:16 Richard Kenner
2001-09-18 10:47 Benjamin Kosnik
2001-09-18 11:54 mike stump
2001-09-18 12:34 ` Joseph S. Myers
2001-09-19 11:28 ` Joe Buck
2001-09-24 9:31 ` law
2001-09-18 17:36 Richard Kenner
2001-10-10 1:12 Wolfgang Bangerth
2001-10-10 1:16 ` Mark Mitchell
2001-10-10 5:14 ` Franz Sirl
2001-10-10 11:08 ` Mark Mitchell
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=E15hg16-0003Dh-00@hzoli.home \
--to=hzoli@hzoli.2y.net \
--cc=gcc@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).