public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-1281] [nvptx] Update comment in 'libgomp.oacc-c-c++-common/parallel-dims.c'
Date: Tue,  8 Jun 2021 09:09:07 +0000 (GMT)	[thread overview]
Message-ID: <20210608090907.EB62C3847813@sourceware.org> (raw)

https://gcc.gnu.org/g:e64d62c7008e6a4b0227fd25e071db8f0b3f1820

commit r12-1281-ge64d62c7008e6a4b0227fd25e071db8f0b3f1820
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Sat Jun 5 22:01:48 2021 +0200

    [nvptx] Update comment in 'libgomp.oacc-c-c++-common/parallel-dims.c'
    
    Small fix-up for r267889 (commit 2b9d9e393766d2fa6e2dd5f361d0db14872cf261)
    "[nvptx] Enable large vectors":
    
    >       * testsuite/libgomp.oacc-c-c++-common/parallel-dims.c: Expect vector
    >       length 2097152 to be reduced to 1024 instead of 32.
    
            libgomp/
            * testsuite/libgomp.oacc-c-c++-common/parallel-dims.c
            <acc_device_nvidia>: Update comment.

Diff:
---
 libgomp/testsuite/libgomp.oacc-c-c++-common/parallel-dims.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libgomp/testsuite/libgomp.oacc-c-c++-common/parallel-dims.c b/libgomp/testsuite/libgomp.oacc-c-c++-common/parallel-dims.c
index ef4917aafff..ef3dfda5fa5 100644
--- a/libgomp/testsuite/libgomp.oacc-c-c++-common/parallel-dims.c
+++ b/libgomp/testsuite/libgomp.oacc-c-c++-common/parallel-dims.c
@@ -385,7 +385,7 @@ int main ()
 	}
       else if (acc_on_device (acc_device_nvidia))
 	{
-	  /* The GCC nvptx back end enforces vector_length (32).  */
+	  /* The GCC nvptx back end reduces to vector_length (1024).  */
 	  vectors_actual = 1024;
 	}
       else if (acc_on_device (acc_device_radeon))


                 reply	other threads:[~2021-06-08  9:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210608090907.EB62C3847813@sourceware.org \
    --to=tschwinge@gcc.gnu.org \
    --cc=gcc-cvs@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).