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 1/2] rs6000: Delete UNSPEC_FRSP
Date: Fri, 06 Sep 2019 19:35:00 -0000 [thread overview]
Message-ID: <e925fcddbdb310835bd41d3b903f68bfa22f8104.1567798092.git.segher@kernel.crashing.org> (raw)
This isn't used since 2012. (It's a remnant of RIOS support).
Committing to trunk.
Segher
2019-09-06 Segher Boessenkool <segher@kernel.crashing.org>
* config/rs6000/rs6000.c (rs6000_rtx_costs) <case UNSPEC>: Delete.
* config/rs6000/rs6000.md (unspec): Delete UNSPEC_FRSP.
---
gcc/config/rs6000/rs6000.c | 12 ------------
gcc/config/rs6000/rs6000.md | 3 +--
2 files changed, 1 insertion(+), 14 deletions(-)
diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/rs6000.c
index ce86d30..c15e05e 100644
--- a/gcc/config/rs6000/rs6000.c
+++ b/gcc/config/rs6000/rs6000.c
@@ -20923,18 +20923,6 @@ rs6000_rtx_costs (rtx x, machine_mode mode, int outer_code,
*total = rs6000_cost->fp;
return false;
- case UNSPEC:
- switch (XINT (x, 1))
- {
- case UNSPEC_FRSP:
- *total = rs6000_cost->fp;
- return true;
-
- default:
- break;
- }
- break;
-
case CALL:
case IF_THEN_ELSE:
if (!speed)
diff --git a/gcc/config/rs6000/rs6000.md b/gcc/config/rs6000/rs6000.md
index b1fddbf..d408e44 100644
--- a/gcc/config/rs6000/rs6000.md
+++ b/gcc/config/rs6000/rs6000.md
@@ -58,8 +58,7 @@ (define_constants
;;
(define_c_enum "unspec"
- [UNSPEC_FRSP ; frsp for POWER machines
- UNSPEC_PROBE_STACK ; probe stack memory reference
+ [UNSPEC_PROBE_STACK ; probe stack memory reference
UNSPEC_TOCPTR ; address of a word pointing to the TOC
UNSPEC_TOC ; address of the TOC (more-or-less)
UNSPEC_TOCSLOT ; offset from r1 of toc pointer save slot
--
1.8.3.1
next reply other threads:[~2019-09-06 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 19:35 Segher Boessenkool [this message]
2019-09-06 19:35 ` [PATCH 2/2] rs6000: Delete UNSPEC_MV_CR_OV 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=e925fcddbdb310835bd41d3b903f68bfa22f8104.1567798092.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).