public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rakdver at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/26290] [4.1 Regression]: code pessimization wrt. GCC 4.0 probably due to TARGET_MEM_REF
Date: Fri, 24 Feb 2006 16:31:00 -0000 [thread overview]
Message-ID: <20060224152029.28955.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26290-5637@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from rakdver at gcc dot gnu dot org 2006-02-24 15:20 -------
Ivopts fail to use the complex addressing mode, thus forcing one more biv into
inner loop. Since this makes it impossible to allocate registers for the loop,
we get another penalty for spilling.
Changing the initial value makes us notice that we may perform IV elimination,
thus getting rid of the extra register.
--
rakdver at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |rakdver at gcc dot gnu dot
|dot org |org
Status|NEW |ASSIGNED
Last reconfirmed|2006-02-19 09:13:57 |2006-02-24 15:20:29
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26290
next prev parent reply other threads:[~2006-02-24 15:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 18:50 [Bug regression/26290] New: [4.1 Regression]: some loop optimizations no longer run at -O2 t dot artem at mailcity dot com
2006-02-14 18:52 ` [Bug regression/26290] " t dot artem at mailcity dot com
2006-02-15 10:58 ` rguenth at gcc dot gnu dot org
2006-02-15 11:19 ` rguenth at gcc dot gnu dot org
2006-02-15 14:43 ` [Bug target/26290] " pinskia at gcc dot gnu dot org
2006-02-17 11:08 ` t dot artem at mailcity dot com
2006-02-18 6:43 ` mmitchel at gcc dot gnu dot org
2006-02-18 14:32 ` steven at gcc dot gnu dot org
2006-02-18 14:36 ` steven at gcc dot gnu dot org
2006-02-18 14:39 ` steven at gcc dot gnu dot org
2006-02-18 14:39 ` steven at gcc dot gnu dot org
2006-02-19 9:13 ` steven at gcc dot gnu dot org
2006-02-19 13:41 ` steven at gcc dot gnu dot org
2006-02-19 13:42 ` steven at gcc dot gnu dot org
2006-02-21 4:56 ` [Bug target/26290] [4.1 Regression]: code pessimization wrt. GCC 4.0 probably due to TARGET_MEM_REF t dot artem at mailcity dot com
2006-02-24 0:30 ` mmitchel at gcc dot gnu dot org
2006-02-24 16:31 ` rakdver at gcc dot gnu dot org [this message]
2006-05-25 2:38 ` mmitchel at gcc dot gnu dot org
2007-02-02 17:02 ` t dot artem at mailcity dot com
2007-02-14 9:10 ` mmitchel at gcc dot gnu dot org
2007-04-19 16:29 ` opruz at centrum dot cz
2007-05-18 7:32 ` t dot artem at mailcity dot com
2007-07-04 21:32 ` [Bug target/26290] [4.1/4.2/4.3 " pinskia at gcc dot gnu dot org
2007-11-04 11:45 ` [Bug target/26290] [4.1/4.2 " rguenth at gcc dot gnu dot org
2007-11-04 13:42 ` t dot artem at mailcity dot com
2007-11-04 14:53 ` rguenth at gcc dot gnu dot org
2008-03-09 19:04 ` t dot artem at mailcity dot com
2008-07-04 20:21 ` [Bug target/26290] [4.2 " jsm28 at gcc dot gnu dot org
2009-03-30 15:48 ` jsm28 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=20060224152029.28955.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).