From: Michael Meissner <meissner@linux.vnet.ibm.com>
To: Michael Meissner <meissner@linux.vnet.ibm.com>,
gcc-patches@gcc.gnu.org, dje.gcc@gmail.com
Subject: Re: [PATCH], Add power9 support to GCC, patch #7 (direct move enhancements)
Date: Mon, 09 Nov 2015 00:49:00 -0000 [thread overview]
Message-ID: <20151109004856.GG17170@ibm-tiger.the-meissners.org> (raw)
In-Reply-To: <20151103202911.GA5304@ibm-tiger.the-meissners.org>
This patch adds support for the new direct move instructions (MFVSRLD and
MTVSRDD) that simplify moving 128-bit data between GPRs and vector registers.
I have built previous versions of this patch with no regressions. At the
moment, I have built a non-bootstrap build and ran the PowerPC tests, with no
regressions. Assuming the bootstrap build that I've started has no
regressions, is it ok to install in the trunk?
[gcc]
2015-11-08 Michael Meissner <meissner@linux.vnet.ibm.com>
* config/rs6000/constraints.md (we constraint): New constraint for
64-bit power9 vector support.
(wL constraint): New constraint for the element in a vector that
can be addressed by the MFVSRLD instruction.
* config/rs6000/rs6000.c (rs6000_debug_reg_global): Add ISA 3.0
debugging.
(rs6000_init_hard_regno_mode_ok): If ISA 3.0 and 64-bit, enable we
constraint. Disable the VSX<->GPR direct move helpers if we have
the MFVSRLD and MTVSRDD instructions.
(rs6000_secondary_reload_simple_move): Add support for doing
vector direct moves directly without additional scratch registers
if we have ISA 3.0 instructions.
(rs6000_secondary_reload_direct_move): Update comments.
(rs6000_output_move_128bit): Add support for ISA 3.0 vector
instructions.
* config/rs6000/vsx.md (vsx_mov<mode>): Add support for ISA 3.0
direct move instructions.
(vsx_movti_64bit): Likewise.
(vsx_extract_<mode>): Likewise.
* config/rs6000/rs6000.h (VECTOR_ELEMENT_MFVSRLD_64BIT): New
macros for ISA 3.0 direct move instructions.
(TARGET_DIRECT_MOVE_128): Likewise.
* config/rs6000/rs6000.md (128-bit GPR splitters): Don't split a
128-bit move that is a direct move between GPR and vector
registers using ISA 3.0 direct move instructions.
* doc/md.texi (RS/6000 constraints): Document we, wF, wG, wL
constraints. Update wa documentation to say not to use %x<n> on
instructions that only take Altivec registers.
[gcc/testsuite]
2015-11-08 Michael Meissner <meissner@linux.vnet.ibm.com>
* gcc.target/powerpc/direct-move-vector.c: New test for 128-bit
vector direct move instructions.
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meissner@linux.vnet.ibm.com, phone: +1 (978) 899-4797
next prev parent reply other threads:[~2015-11-09 0:49 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 20:29 [PATCH], Add power9 support to GCC, patch #1 Michael Meissner
2015-11-04 21:16 ` Segher Boessenkool
2015-11-04 21:27 ` Michael Meissner
2015-11-09 0:33 ` [PATCH], Add power9 support to GCC, patch #1 (revised) Michael Meissner
2015-11-09 16:12 ` David Edelsohn
2015-11-10 18:39 ` [PATCH], Add power9 support to GCC, patch #8 (add integer multiply/add) Michael Meissner
2015-11-12 20:39 ` David Edelsohn
2015-11-09 0:36 ` [PATCH], Add power9 support to GCC, patch #2 (add modulus instructions) Michael Meissner
2015-11-09 15:48 ` Segher Boessenkool
2015-11-09 18:07 ` Michael Meissner
2015-11-09 16:14 ` David Edelsohn
2015-11-10 0:17 ` [PATCH], Add power9 support to GCC, patches #2-5 committed Michael Meissner
2015-11-10 0:20 ` Michael Meissner
2015-11-09 0:38 ` [PATCH], Add power9 support to GCC, patch #3 (scalar count trailing zeros) Michael Meissner
2015-11-09 15:59 ` Segher Boessenkool
2015-11-09 17:18 ` Michael Meissner
2015-11-09 19:33 ` Segher Boessenkool
2015-11-09 18:02 ` David Edelsohn
2015-11-09 0:39 ` [PATCH], Add power9 support to GCC, patch #4 Michael Meissner
2015-11-09 16:29 ` Segher Boessenkool
2015-11-09 17:27 ` Michael Meissner
2015-11-09 19:48 ` Segher Boessenkool
2015-11-09 18:03 ` David Edelsohn
2015-11-09 0:42 ` [PATCH], Add power9 support to GCC, patch #5 (ISA 3.0 fusion) Michael Meissner
2015-11-09 17:16 ` Segher Boessenkool
2015-11-09 17:34 ` Michael Meissner
2015-11-09 19:57 ` Segher Boessenkool
2015-11-09 21:11 ` David Edelsohn
2015-11-09 22:17 ` Michael Meissner
2015-11-09 22:33 ` David Edelsohn
2015-11-09 18:57 ` David Edelsohn
2015-11-14 22:58 ` Segher Boessenkool
2015-11-09 0:45 ` [PATCH], Add power9 support to GCC, patch #6 (IEEE 128-bit hardware support) Michael Meissner
2015-11-09 19:29 ` Segher Boessenkool
2015-11-10 0:41 ` Joseph Myers
2015-11-10 18:41 ` Michael Meissner
2015-11-12 20:47 ` David Edelsohn
2015-11-13 22:13 ` [PATCH applied], Power9 patches #6-8 (IEEE 128-bit h/w, 128-bit direct move, integer mult/add) Michael Meissner
2015-11-09 0:49 ` Michael Meissner [this message]
2015-11-09 20:00 ` [PATCH], Add power9 support to GCC, patch #7 (direct move enhancements) Segher Boessenkool
2015-11-09 21:06 ` Michael Meissner
2015-11-12 20:43 ` David Edelsohn
2015-11-10 20:56 ` [PATCH, applied], Add power9 support to GCC, patch #9 (config.gcc) Michael Meissner
2015-11-10 21:56 ` [PATCH], Add power9 support to GCC, patch #10 (SFmode/DFmode d-form addressing) Michael Meissner
2015-11-11 0:19 ` Segher Boessenkool
2015-11-11 0:26 ` Michael Meissner
2015-11-24 18:08 ` David Edelsohn
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=20151109004856.GG17170@ibm-tiger.the-meissners.org \
--to=meissner@linux.vnet.ibm.com \
--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).