From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: dje.gcc@gmail.com, Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH 01/12] @neg<mode>2
Date: Mon, 01 Jul 2019 18:01:00 -0000 [thread overview]
Message-ID: <1b3393adbbed5efbb6e0464b486d6fd9f7e65719.1561994239.git.segher@kernel.crashing.org> (raw)
In-Reply-To: <cover.1561994239.git.segher@kernel.crashing.org>
In-Reply-To: <cover.1561994239.git.segher@kernel.crashing.org>
2019-07-01 Segher Boessenkool <segher@kernel.crashing.org>
* config/rs6000/rs6000.md (neg<mode>2): Make this a parameterized name.
(allocate_stack): Use that name. Simplify.
---
gcc/config/rs6000/rs6000.md | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/gcc/config/rs6000/rs6000.md b/gcc/config/rs6000/rs6000.md
index d0d272a..63823c4 100644
--- a/gcc/config/rs6000/rs6000.md
+++ b/gcc/config/rs6000/rs6000.md
@@ -2249,7 +2249,7 @@ (define_insn "subf<mode>3_carry_in_xx"
[(set_attr "type" "add")])
-(define_insn "neg<mode>2"
+(define_insn "@neg<mode>2"
[(set (match_operand:GPR 0 "gpc_reg_operand" "=r")
(neg:GPR (match_operand:GPR 1 "gpc_reg_operand" "r")))]
""
@@ -9810,10 +9810,7 @@ (define_expand "allocate_stack"
{
operands[1] = force_reg (Pmode, operands[1]);
neg_op0 = gen_reg_rtx (Pmode);
- if (TARGET_32BIT)
- emit_insn (gen_negsi2 (neg_op0, operands[1]));
- else
- emit_insn (gen_negdi2 (neg_op0, operands[1]));
+ emit_insn (gen_neg2 (Pmode, neg_op0, operands[1]));
}
else
neg_op0 = GEN_INT (-INTVAL (operands[1]));
--
1.8.3.1
next prev parent reply other threads:[~2019-07-01 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 18:00 [PATCH 00/12] rs6000: Use parameterised names Segher Boessenkool
2019-07-01 18:01 ` Segher Boessenkool [this message]
2019-07-01 18:24 ` [PATCH 02/12] @fix_trunc<mode>si2_fprs Segher Boessenkool
2019-07-01 18:25 ` [PATCH 03/12] @abs<mode>2_internal Segher Boessenkool
2019-07-01 18:26 ` [PATCH 08/12] @extenddf<mode>2 Segher Boessenkool
2019-07-01 18:26 ` [PATCH 05/12] @ctr<mode> Segher Boessenkool
2019-07-01 18:26 ` [PATCH 07/12] @extenddf<mode>2_{fprs,vsx} Segher Boessenkool
2019-07-01 18:26 ` [PATCH 04/12] @indirect_jump<mode>_nospec Segher Boessenkool
2019-07-01 18:26 ` [PATCH 06/12] @eh_set_lr_<mode> Segher Boessenkool
2019-07-01 18:27 ` [PATCH 11/12] @ieee_128bit_vsx_neg<mode>2 Segher Boessenkool
2019-07-01 18:27 ` [PATCH 09/12] @neg<mode>2_hw Segher Boessenkool
2019-07-01 18:27 ` [PATCH 12/12] @ieee_128bit_vsx_abs<mode>2 Segher Boessenkool
2019-07-01 18:27 ` [PATCH 10/12] @abs<mode>2_hw Segher Boessenkool
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=1b3393adbbed5efbb6e0464b486d6fd9f7e65719.1561994239.git.segher@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.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).