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 target/55303] [SH] Add support for clips / clipu instructions
Date: Mon, 06 May 2013 05:48:00 -0000	[thread overview]
Message-ID: <bug-55303-4-AUJsdxXux4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55303-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #3 from Oleg Endo <olegendo at gcc dot gnu.org> 2013-05-06 05:48:18 UTC ---
(In reply to comment #1)
> I will modify the attached patch so that it will allow only the HW clip
> constants for now.

This has been committed as rev 198617:
http://gcc.gnu.org/viewcvs/gcc?view=revision&revision=198617

    PR target/55303
    * config/sh/sh.c (sh_rtx_costs): Handle SMIN and SMAX cases.
    * config/sh/sh.md (*clips, uminsi3, *clipu, clipu_one): New insns and
    related expanders.
    * config/sh/iterators.md (SMIN_SMAX): New code iterator.
    * config/sh/predicates.md (arith_reg_or_0_or_1_operand,
    clips_min_const_int, clips_max_const_int, clipu_max_const_int):
    New predicates.

    PR target/55303
    * gcc.target/sh/pr55303-1.c: New.
    * gcc.target/sh/pr55303-2.c: New.
    * gcc.target/sh/pr55303-3.c: New.


      parent reply	other threads:[~2013-05-06  5:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  0:31 [Bug target/55303] New: " olegendo at gcc dot gnu.org
2013-03-02 16:17 ` [Bug target/55303] " olegendo at gcc dot gnu.org
2013-03-02 16:24 ` olegendo at gcc dot gnu.org
2013-05-06  5:48 ` olegendo at gcc dot gnu.org [this message]

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