public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19201] [m68k] Inefficient code for array accesses (from old PROBLEMS)
Date: Sat, 26 Feb 2011 12:33:00 -0000 [thread overview]
Message-ID: <bug-19201-4-wea1zy7uO5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-19201-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19201
Mikael Pettersson <mikpe at it dot uu.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpe at it dot uu.se
--- Comment #14 from Mikael Pettersson <mikpe at it dot uu.se> 2011-02-26 11:35:50 UTC ---
(In reply to comment #13)
> Also fine, not closed. Great to see that you pay enough attention to stop the
> reporter from closing his own PRs. I wish you would be just as fast with
> actually doing something about them. It is not even clear whether these
> problems still exist!
The missed optimization still occurs with gcc-4.6, which generates:
f:
move.l 4(%sp),%a0
move.l (%a0),%a1
move.l 4(%a0),%d0
clr.b (%a1,%d0.l)
rts
.size f, .-f
.ident "GCC: (GNU) 4.6.0 20110219 (experimental)"
I'll try Kazu's patch in my next 4.4 bootstrap/regtest.
next prev parent reply other threads:[~2011-02-26 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19201-4@http.gcc.gnu.org/bugzilla/>
2011-02-25 23:13 ` steven at gcc dot gnu.org
2011-02-25 23:58 ` schwab@linux-m68k.org
2011-02-26 3:44 ` steven at gcc dot gnu.org
2011-02-26 12:33 ` mikpe at it dot uu.se [this message]
2011-02-28 12:37 ` mikpe at it dot uu.se
[not found] <bug-19201-280@http.gcc.gnu.org/bugzilla/>
2005-11-19 21:52 ` kazu at gcc dot gnu dot org
2005-11-20 0:22 ` kazu at gcc dot gnu dot org
2005-11-21 23:07 ` schwab at suse dot de
2005-11-22 17:43 ` kazu at gcc dot gnu dot org
2007-12-17 8:12 ` steven at gcc dot gnu dot org
2008-09-03 2:06 ` pinskia at gcc dot gnu dot org
2008-09-21 13:22 ` steven at gcc dot gnu dot org
2010-02-12 22:01 ` steven at gcc dot gnu dot org
2004-12-30 12:15 [Bug target/19201] New: " steven at gcc dot gnu dot org
2004-12-31 13:32 ` [Bug target/19201] " schwab at suse dot de
2004-12-31 14:58 ` 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=bug-19201-4-wea1zy7uO5@http.gcc.gnu.org/bugzilla/ \
--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).