From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] doc: Remove HSAIL from Language Standards
Date: Mon, 28 Dec 2020 21:51:26 +0100 (CET) [thread overview]
Message-ID: <20201228205131.A82DD33E4A@hamza.pair.com> (raw)
Pushed.
There's quite a number of further references in gcc/doc; is anyone
planning on continuing the deprecation and removing the actual bits?
Gerald
commit 7e999bd84f47205dc44b0f2dc90b53b3c888ca48
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date: Mon Dec 28 21:41:55 2020 +0100
doc: Remove HSAIL from Language Standards
Support for HSAIL has been deprecated with GCC 10 and their web server
has been down for weeks.
gcc/
2020-12-28 Gerald Pfeifer <gerald@pfeifer.com>
* doc/standards.texi (HSAIL): Remove section.
diff --git a/gcc/doc/standards.texi b/gcc/doc/standards.texi
index fc5016028dd..974f9b7e46d 100644
--- a/gcc/doc/standards.texi
+++ b/gcc/doc/standards.texi
@@ -312,14 +312,6 @@ available online, see @uref{http://gcc.gnu.org/readings.html}
As of the GCC 4.7.1 release, GCC supports the Go 1 language standard,
described at @uref{https://golang.org/doc/go1}.
-@section HSA Intermediate Language (HSAIL)
-
-GCC can compile the binary representation (BRIG) of the HSAIL text format as
-described in HSA Programmer's Reference Manual version 1.0.1. This
-capability is typically utilized to implement the HSA runtime API's HSAIL
-finalization extension for a gcc supported processor. HSA standards are
-freely available at @uref{http://www.hsafoundation.com/standards/}.
-
@section D language
GCC supports the D 2.0 programming language. The D language itself is
next reply other threads:[~2020-12-28 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 20:51 Gerald Pfeifer [this message]
2020-12-29 22:29 ` Martin Jambor
2020-12-29 22:50 ` Gerald Pfeifer
2021-01-04 15:22 ` Martin Jambor
2021-01-06 0:03 ` Gerald Pfeifer
2021-01-26 18:35 ` [PATCH] Deprecate the BRIG/HSAIL front-end (Was: Re: [committed] doc: Remove HSAIL from Language Standards) Martin Jambor
2021-01-26 21:53 ` 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=20201228205131.A82DD33E4A@hamza.pair.com \
--to=gerald@pfeifer.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).