public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/36770] PowerPC missed autoincrement opportunity
Date: Fri, 11 Jul 2008 11:56:00 -0000 [thread overview]
Message-ID: <20080711115608.9799.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36770-16150@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from bonzini at gnu dot org 2008-07-11 11:56 -------
Yes, the code produced shows that something (probably fwprop, I trust Andrew
though I'd like to see dumps) is turning the GIMPLE code
temp = a[0];
a[1] = temp;
temp++;
into something harder to optimize. It might be also a pass-ordering problem.
--
bonzini at gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Summary|PowerPC generated PTR code |PowerPC missed autoincrement
|inefficiency |opportunity
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36770
next prev parent reply other threads:[~2008-07-11 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 14:57 [Bug c/36770] New: PowerPC generated PTR code ineffiency gunnar at greyhound-data dot com
2008-07-09 18:23 ` [Bug middle-end/36770] " pinskia at gcc dot gnu dot org
2008-07-10 9:19 ` [Bug middle-end/36770] PowerPC generated PTR code inefficiency gunnar at greyhound-data dot com
2008-07-11 11:56 ` bonzini at gnu dot org [this message]
2008-07-18 13:42 ` [Bug middle-end/36770] PowerPC missed autoincrement opportunity bonzini at gnu dot org
2008-07-18 14:14 ` bonzini at gnu dot org
[not found] <bug-36770-4@http.gcc.gnu.org/bugzilla/>
2013-12-24 23:13 ` steven at gcc dot gnu.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=20080711115608.9799.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).