From: "Greta Yorsh" <greta.yorsh@arm.com>
To: "GCC Patches" <gcc-patches@gcc.gnu.org>
Cc: "Ramana Radhakrishnan" <Ramana.Radhakrishnan@arm.com>,
"Richard Earnshaw" <Richard.Earnshaw@arm.com>
Subject: [PATCH,ARM] Set attribute predicable
Date: Thu, 14 Feb 2013 13:54:00 -0000 [thread overview]
Message-ID: <000d01ce0aba$bb75afd0$32610f70$@yorsh@arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
This patch sets attribute "predicable" to "yes" for patterns that handle add
with carry and already use %? in their output statements.
Ok for trunk?
Thanks,
Greta
gcc/
2013-02-14 Greta Yorsh <Greta.Yorsh@arm.com>
* config/arm/arm.md (addsi3_carryin_<optab>): Set attribute
"predicable" to yes.
(addsi3_carryin_alt2_<optab>,addsi3_carryin_shift_<optab>):
Likewise.
[-- Attachment #2: predicable-attr.patch.txt --]
[-- Type: text/plain, Size: 1090 bytes --]
diff --git a/gcc/config/arm/arm.md b/gcc/config/arm/arm.md
index 1cb1515b1fa57c6052b68eb8701616c1b80e7416..35294dd6560ac63279d95eca6cf774257e06bd93 100644
--- a/gcc/config/arm/arm.md
+++ b/gcc/config/arm/arm.md
@@ -974,7 +974,8 @@ (define_insn "*addsi3_carryin_<optab>"
"@
adc%?\\t%0, %1, %2
sbc%?\\t%0, %1, #%B2"
- [(set_attr "conds" "use")]
+ [(set_attr "conds" "use")
+ (set_attr "predicable" "yes")]
)
(define_insn "*addsi3_carryin_alt2_<optab>"
@@ -986,7 +987,8 @@ (define_insn "*addsi3_carryin_alt2_<opta
"@
adc%?\\t%0, %1, %2
sbc%?\\t%0, %1, #%B2"
- [(set_attr "conds" "use")]
+ [(set_attr "conds" "use")
+ (set_attr "predicable" "yes")]
)
(define_insn "*addsi3_carryin_shift_<optab>"
@@ -1000,6 +1002,7 @@ (define_insn "*addsi3_carryin_shift_<opt
"TARGET_32BIT"
"adc%?\\t%0, %1, %3%S2"
[(set_attr "conds" "use")
+ (set_attr "predicable" "yes")
(set (attr "type") (if_then_else (match_operand 4 "const_int_operand" "")
(const_string "alu_shift")
(const_string "alu_shift_reg")))]
next reply other threads:[~2013-02-14 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 13:54 Greta Yorsh [this message]
2013-02-14 15:57 ` Richard Earnshaw
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='000d01ce0aba$bb75afd0$32610f70$@yorsh@arm.com' \
--to=greta.yorsh@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.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).