From: David Edelsohn <dje.gcc@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 7/9] rs6000: Remove FIXED_SCRATCH
Date: Tue, 13 Jun 2017 13:22:00 -0000 [thread overview]
Message-ID: <CAGWvnyn+KREDVNhczO60xc=MWQ4Av-1Vij3wPiOK-qny-SB9Yg@mail.gmail.com> (raw)
In-Reply-To: <9828f2505d38efefd08095c11d9380bca47c3c60.1497353003.git.segher@kernel.crashing.org>
On Tue, Jun 13, 2017 at 8:53 AM, Segher Boessenkool
<segher@kernel.crashing.org> wrote:
> 2017-06-13 Segher Boessenkool <segher@kernel.crashing.org>
>
> * config/rs6000/rs6000.h (FIXED_SCRATCH): Delete.
Okay.
Thanks, david
next prev parent reply other threads:[~2017-06-13 13:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 12:53 [PATCH 0/9] rs6000: SPE removal, part 2 Segher Boessenkool
2017-06-13 12:53 ` [PATCH 3/9] rs6000: Remove t-spe Segher Boessenkool
2017-06-13 13:20 ` David Edelsohn
2017-06-13 12:53 ` [PATCH 4/9] rs6000: Remove eabispe.h Segher Boessenkool
2017-06-13 13:21 ` David Edelsohn
2017-06-13 12:53 ` [PATCH 5/9] rs6000: Updates to t-linux Segher Boessenkool
2017-06-13 13:21 ` David Edelsohn
2017-06-13 12:53 ` [PATCH 1/9] rs6000: Sanitize vector modes Segher Boessenkool
2017-06-13 13:19 ` David Edelsohn
2017-06-13 12:54 ` [PATCH 7/9] rs6000: Remove FIXED_SCRATCH Segher Boessenkool
2017-06-13 13:22 ` David Edelsohn [this message]
2017-06-13 12:54 ` [PATCH 9/9] rs6000: Comment fixes + some leftovers Segher Boessenkool
2017-06-13 13:23 ` David Edelsohn
2017-06-13 12:54 ` [PATCH 2/9] rs6000: Remove SPE_CONST_OFFSET_OK Segher Boessenkool
2017-06-13 13:20 ` David Edelsohn
2017-06-13 12:54 ` [PATCH 6/9] rs6000: Updates to t-rtems Segher Boessenkool
2017-06-13 13:21 ` David Edelsohn
2017-06-13 12:54 ` [PATCH 8/9] rs6000: Remove VECTOR_SPE Segher Boessenkool
2017-06-13 13:22 ` 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='CAGWvnyn+KREDVNhczO60xc=MWQ4Av-1Vij3wPiOK-qny-SB9Yg@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).