From: James Bowman <james.bowman@ftdichip.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [patch committed FT32] Pattern for CC to register move
Date: Fri, 13 Nov 2015 01:44:00 -0000 [thread overview]
Message-ID: <CA9BBF0458F83C4F9051448B941B57D11C2C5BBD@glaexch3> (raw)
The attached patch adds a pattern for CC to register move.
[gcc]
2015-11-11 James Bowman <james.bowman@ftdichip.com>
* config/ft32/ft32.md: New pattern *sne
Index: gcc/config/ft32/ft32.md
===================================================================
--- gcc/config/ft32/ft32.md (revision 230144)
+++ gcc/config/ft32/ft32.md (working copy)
@@ -255,6 +255,13 @@
;; SImode
+(define_insn "*sne"
+ [(set (match_operand:SI 0 "register_operand" "=r")
+ (reg:SI CC_REG))]
+ ""
+ "bextu.l %0,$cc,32|0\;xor.l %0,%0,-1"
+)
+
;; Push a register onto the stack
(define_insn "movsi_push"
[(set (mem:SI (pre_dec:SI (reg:SI SP_REG)))
@@ -884,6 +891,7 @@
DONE;
})
+
(define_expand "epilogue"
[(return)]
""
reply other threads:[~2015-11-13 1:44 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=CA9BBF0458F83C4F9051448B941B57D11C2C5BBD@glaexch3 \
--to=james.bowman@ftdichip.com \
--cc=gcc-patches@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).