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 0/3] rs6000: Some updates for rotate etc.
Date: Mon, 20 Jul 2015 16:13:00 -0000 [thread overview]
Message-ID: <cover.1437404023.git.segher@kernel.crashing.org> (raw)
Hi all,
Two updates for the rotate revamp, and a third patch that won't apply
without it. I'll fold the first two together with the big patch, if
approved.
Everything bootstrapped and tested on powerpc64-linux, as usual; no
regressions.
Segher
Segher Boessenkool (3):
Doc fixes for rot
Fix shift amount (GPR->SI)
lt0_disi
gcc/config/rs6000/constraints.md | 2 +-
gcc/config/rs6000/rs6000.md | 35 +++++++++++++++++++++++------------
gcc/doc/md.texi | 12 ------------
3 files changed, 24 insertions(+), 25 deletions(-)
--
1.8.1.4
next reply other threads:[~2015-07-20 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 16:13 Segher Boessenkool [this message]
2015-07-20 16:13 ` [PATCH 1/3] Doc fixes for rot Segher Boessenkool
2015-07-20 16:19 ` David Edelsohn
2015-07-20 16:14 ` [PATCH 2/3] Fix shift amount (GPR->SI) Segher Boessenkool
2015-07-20 16:20 ` David Edelsohn
2015-07-20 16:18 ` [PATCH 3/3] lt0_disi Segher Boessenkool
2015-07-20 16:24 ` 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=cover.1437404023.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).