public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tobias Burnus <tobias@codesourcery.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch][wwwdocs + gcc] nvptx – update for -mptx change – gcc-12/changes.html + gcc/docs/invoke.texi
Date: Fri, 4 Feb 2022 12:46:49 +0100	[thread overview]
Message-ID: <256b733f-0378-9445-3c2b-45825e731202@suse.de> (raw)
In-Reply-To: <f069981d-5a0c-11d5-db2d-ea4574037eb0@codesourcery.com>

On 2/2/22 09:30, Tobias Burnus wrote:
> This patch updates the documentation for Tom's change of the default
> -mptx= version - mentioning also -mptx=7.0.
> 
> I forgot whether ptx = 7.0 was working fine or whether there was
> a reason not to mention it.

A ptx version is experimental if all sm versions it enables are 
experimental.

7.0 enables sm_80, and that one is experimental.

sm_80 is considered experimental, because the last time I tried to do a 
gcc build with the default set to sm_80, it failed (ICEs).  Likewise 
sm_75, sm_53.

Following that reasoning ptx isa 6.3 would also be experimental, but it 
fixes something that is very fragile with older ptx version (warp 
convergence) so it has been promoted to supported.

Anyway, I'm preparing a patch that picks default -mptx based on -misa, 
with a default minimum of 6.0 instead of 6.3, to enable testing with a 
390.x driver.

> At some point, we also have to update -misa=... Currently, only
> sm_30 and sm_35 are documented but sm_53, sm_75 and sm_80 are supported.
> Can they now be documented are are there still issues?

AFAIK there are still issues.

> OK to commit the wwwdocs + gcc invoke.texi patches?

Sorry, it looks like this is still in flux.

Thanks,
- Tom

      reply	other threads:[~2022-02-04 11:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  8:30 Tobias Burnus
2022-02-04 11:46 ` Tom de Vries [this message]

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=256b733f-0378-9445-3c2b-45825e731202@suse.de \
    --to=tdevries@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tobias@codesourcery.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).