public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52049] SH Target: Inefficient constant address access
Date: Mon, 30 Jan 2012 07:15:00 -0000	[thread overview]
Message-ID: <bug-52049-4-fC7Wkrccdw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52049-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52049

--- Comment #1 from Kazumoto Kojima <kkojima at gcc dot gnu.org> 2012-01-30 00:15:16 UTC ---
(In reply to comment #0)
> I'm not sure whether this is actually a problem of the SH back-end or of some
> middle-end passes.  It happens for all sub-targets and regardless of the
> endianess.

I've tried these cases on arm/thumb and got similar results
which look not very good.  From the rtl dumps, it looks a general
issue with postreload optimization on some targets.


  reply	other threads:[~2012-01-30  0:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-29 22:45 [Bug target/52049] New: " oleg.endo@t-online.de
2012-01-30  7:15 ` kkojima at gcc dot gnu.org [this message]
2012-02-26 23:41 ` [Bug target/52049] " olegendo at gcc dot gnu.org
2015-05-22 13:58 ` olegendo 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=bug-52049-4-fC7Wkrccdw@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).