public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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 00/12] rs6000: Use parameterised names
Date: Mon, 01 Jul 2019 18:00:00 -0000	[thread overview]
Message-ID: <cover.1561994239.git.segher@kernel.crashing.org> (raw)

This series makes the rs6000 backend use parameterised names.  This
means adding an "@" to the start of pattern names, removing the mode
from the gen_* names where you call them, and adding an extra mode
parameter to those calls (as the first argument).

The abs and neg patterns used to call FAIL for some unexpected modes,
they no longer do.  It should have maybe used gcc_unreachable there
instead.  These patches also remove such gcc_unreachable.

Tested all on powerpc64-linux {-m32,-m64} and on p9 powerpc64le-linux.
Committing to trunk.


Segher


Segher Boessenkool (12):
  @neg<mode>2
  @fix_trunc<mode>si2_fprs
  @abs<mode>2_internal
  @indirect_jump<mode>_nospec
  @ctr<mode>
  @eh_set_lr_<mode>
  @extenddf<mode>2_{fprs,vsx}
  @extenddf<mode>2
  @neg<mode>2_hw
  @abs<mode>2_hw
  @ieee_128bit_vsx_neg<mode>2
  @ieee_128bit_vsx_abs<mode>2

 gcc/config/rs6000/rs6000.md | 130 +++++++++++---------------------------------
 1 file changed, 33 insertions(+), 97 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2019-07-01 18:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 18:00 Segher Boessenkool [this message]
2019-07-01 18:01 ` [PATCH 01/12] @neg<mode>2 Segher Boessenkool
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 05/12] @ctr<mode> Segher Boessenkool
2019-07-01 18:26 ` [PATCH 08/12] @extenddf<mode>2 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:26 ` [PATCH 07/12] @extenddf<mode>2_{fprs,vsx} Segher Boessenkool
2019-07-01 18:27 ` [PATCH 09/12] @neg<mode>2_hw Segher Boessenkool
2019-07-01 18:27 ` [PATCH 11/12] @ieee_128bit_vsx_neg<mode>2 Segher Boessenkool
2019-07-01 18:27 ` [PATCH 10/12] @abs<mode>2_hw Segher Boessenkool
2019-07-01 18:27 ` [PATCH 12/12] @ieee_128bit_vsx_abs<mode>2 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=cover.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).