public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/55306] New: Make combine emit converted logical right shifts
Date: Tue, 13 Nov 2012 01:13:00 -0000	[thread overview]
Message-ID: <bug-55306-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55306
           Summary: Make combine emit converted logical right shifts
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: rtl-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: olegendo@gcc.gnu.org


As of rev 193423 the combine pass can successfully convert arithmetic right
shifts into logical right shifts, but will not split / emit them as individual
insns if ...
* the target has arith. right shift patterns defined that match the shift
* the target does not have an insn that combine came up with, which inlcudes
  the logical shift.

There are some targets (SH, ARC, see PR 54089) where logical right shifts are
cheaper than arithmetic right shifts.
Since combine already has shift conversion integrated, it would probably make
sense to extend it, instead of replicating it in some separate pass or doing
fancy stuff in the target code.
Ideally, whenever combine converts a arith shift into a logical shift it should
look at the costs of the shifts and always split out the cheaper shift insn (if
the target has a pattern for the logical shift).


                 reply	other threads:[~2012-11-13  1:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-55306-4@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).