From: "Harwath, Frederik" <frederik@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>,
Tobias Burnus <tobias@codesourcery.com>,
"Stubbs, Andrew" <ams@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH, committed][OpenACC] Adapt libgomp acc_get_property.f90 test
Date: Fri, 21 Feb 2020 14:46:00 -0000 [thread overview]
Message-ID: <4637edb9-a83f-0f1e-0410-79e8a3907bda@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 360 bytes --]
Hi,
The commit r10-6721-g8d1a1cb1b816381bf60cb1211c93b8eba1fe1472 has changed
the name of the type that is used for the return value of the Fortran
acc_get_property function without adapting the test acc_get_property.f90.
This obvious patch fixes that problem. Committed as r10-6782-g83d45e1d7155a5a600d8a4aa01aca00d3c6c2d3a.
Best regards,
Frederik
[-- Attachment #2: 0001-Adapt-libgomp-acc_get_property.f90-test.patch --]
[-- Type: text/x-patch, Size: 2275 bytes --]
From 83d45e1d7155a5a600d8a4aa01aca00d3c6c2d3a Mon Sep 17 00:00:00 2001
From: Frederik Harwath <frederik@codesourcery.com>
Date: Fri, 21 Feb 2020 15:26:02 +0100
Subject: [PATCH] Adapt libgomp acc_get_property.f90 test
The commit r10-6721-g8d1a1cb1b816381bf60cb1211c93b8eba1fe1472 has changed
the name of the type that is used for the return value of the Fortran
acc_get_property function without adapting the test acc_get_property.f90.
2020-02-21 Frederik Harwath <frederik@codesourcery.com>
* testsuite/libgomp.oacc-fortran/acc_get_property.f90: Adapt to
changes from 2020-02-19, i.e. use integer(c_size_t) instead of
integer(acc_device_property) for the type of the return value of
acc_get_property.
---
libgomp/ChangeLog | 7 +++++++
.../testsuite/libgomp.oacc-fortran/acc_get_property.f90 | 3 ++-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/libgomp/ChangeLog b/libgomp/ChangeLog
index 3c640c7350b..bff3ae58c9a 100644
--- a/libgomp/ChangeLog
+++ b/libgomp/ChangeLog
@@ -1,3 +1,10 @@
+2020-02-21 Frederik Harwath <frederik@codesourcery.com>
+
+ * testsuite/libgomp.oacc-fortran/acc_get_property.f90: Adapt to
+ changes from 2020-02-19, i.e. use integer(c_size_t) instead of
+ integer(acc_device_property) for the type of the return value of
+ acc_get_property.
+
2020-02-19 Tobias Burnus <tobias@codesourcery.com>
* .gitattributes: New; whitespace handling for Fortran's openacc_lib.h.
diff --git a/libgomp/testsuite/libgomp.oacc-fortran/acc_get_property.f90 b/libgomp/testsuite/libgomp.oacc-fortran/acc_get_property.f90
index 80ae292f41f..1af7cc3b988 100644
--- a/libgomp/testsuite/libgomp.oacc-fortran/acc_get_property.f90
+++ b/libgomp/testsuite/libgomp.oacc-fortran/acc_get_property.f90
@@ -26,13 +26,14 @@ end program test
! and do basic device independent validation.
subroutine print_device_properties (device_type)
use openacc
+ use iso_c_binding, only: c_size_t
implicit none
integer, intent(in) :: device_type
integer :: device_count
integer :: device
- integer(acc_device_property) :: v
+ integer(c_size_t) :: v
character*256 :: s
device_count = acc_get_num_devices(device_type)
--
2.17.1
reply other threads:[~2020-02-21 14:46 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=4637edb9-a83f-0f1e-0410-79e8a3907bda@codesourcery.com \
--to=frederik@codesourcery.com \
--cc=ams@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=thomas@codesourcery.com \
--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).