public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [committed] doc: Remove HSAIL from Language Standards
Date: Wed, 6 Jan 2021 01:03:43 +0100 (CET)	[thread overview]
Message-ID: <5bddfdee-ed57-f03-1a60-3b362ae135f9@pfeifer.com> (raw)
In-Reply-To: <ri6im8c4thv.fsf@suse.cz>

On Mon, 4 Jan 2021, Martin Jambor wrote:
> I trust you that HSA Foundation's web server was down for weeks but it
> is not down now, http://www.hsafoundation.com/standards/ loads for me
> fine and "HSA Programmer Reference Manual Specification 1.01" available
> from that page describes the HSAIL that the FE implements.

Thanks for checking that again, Martin. I have applied the patch
below, reverting the original commit.

> Given that nobody bothered to update the FE to HSAIL 1.2 (which is 2.5
> years old) and it is unlikely to have many users, maybe it is time to
> deprecate the FE in GCC 11 (I guess it is not a promise to remove it in
> 12), but that is a different question.

I think I'd recommend that, yes.

Cheers, Gerald


commit ad92bf4b165935b58195825dc8f089f53fd2710b
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Wed Jan 6 00:56:55 2021 +0100

    doc: Re-add HSAIL to Language Standards
    
    The HSAIL web server has reappeared after weeks, so restore the standard
    reference for now while we consider further deprecation.
    
    This reverts commit 7e999bd84f47205dc44b0f2dc90b53b3c888ca48.
    
    gcc/
    2021-01-06  Gerald Pfeifer  <gerald@pfeifer.com>
    
            Revert:
            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 128b1c67bbc..0f88333eec6 100644
--- a/gcc/doc/standards.texi
+++ b/gcc/doc/standards.texi
@@ -320,6 +320,14 @@ 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

  reply	other threads:[~2021-01-06  0:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 20:51 Gerald Pfeifer
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 [this message]
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=5bddfdee-ed57-f03-1a60-3b362ae135f9@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    /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).