From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: gerald@pfeifer.com
Subject: wwwdocs: Some release notes for powerpc for GCC 8
Date: Thu, 01 Feb 2018 13:34:00 -0000 [thread overview]
Message-ID: <20180201133350.GZ21977@gate.crashing.org> (raw)
Hi!
This is a first set of release notes for Power for GCC 8.
Is this okay to commit?
Segher
Index: htdocs/gcc-8/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-8/changes.html,v
retrieving revision 1.31
diff -u -3 -p -r1.31 changes.html
--- htdocs/gcc-8/changes.html 23 Jan 2018 14:02:45 -0000 1.31
+++ htdocs/gcc-8/changes.html 1 Feb 2018 13:28:08 -0000
@@ -374,6 +374,8 @@ a work-in-progress.</h2>
</li>
</ul>
+<!-- <h3 id="nvptx">NVPTX</h3> -->
+
<h3 id="hppa">PA-RISC</h3>
<ul>
<li>
@@ -387,13 +389,26 @@ a work-in-progress.</h2>
</li>
</ul>
-<!-- <h3 id="nvptx">NVPTX</h3> -->
-
<h3 id="powerpc">PowerPC / PowerPC64 / RS6000</h3>
<ul>
- <li></li>
+ <li>
+ The PowerPC SPE support is split off to a separate <code>powerpcspe</code>
+ port. See the separate entry for that new port.
+ </li>
+ <li>
+ The Paired Single support (as used on some PPC750 CPUs,
+ <code>-mpaired</code>, <code>powerpc*-*-linux*paired*</code>)
+ is deprecated and will be removed in a future release.
+ </li>
+ <li>
+ The Xilinx floating point support (<code>-mxilinx-fpu</code>,
+ <code>powerpc-xilinx-eabi*</code>)
+ is deprecated and will be removed in a future release.
+ </li>
</ul>
+<h3 id="powerpcspe">PowerPC SPE</h3>
+
<!-- <h3 id="s390">S/390, System z, IBM z Systems</h3> -->
<!-- <h3 id="riscv">RISC-V</h3> -->
next reply other threads:[~2018-02-01 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 13:34 Segher Boessenkool [this message]
2018-02-01 16:07 ` Gerald Pfeifer
2018-02-01 17:03 ` Segher Boessenkool
2018-02-06 21:26 ` Gerald Pfeifer
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=20180201133350.GZ21977@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/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).