On Wed, Mar 04, 2020 at 08:27:10PM +0100, Thomas Schwinge wrote:
> ... which as of PR89433 commit b48f44bf77a39fefc238a16cf1225c6464c82406 causes
> an ICE. Not sure if this is actually supposed to be valid or invalid code.
> Until the interactions between OpenACC and OpenMP 'target' get defined
>
-
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander
Walter
--- Begin Message ---
Hi!
On 2019-05-17T21:16:57+0200, I wrote:
> Now committed to trunk in [...]
> r271345 "[PR894
Hi!
On Fri, 22 Feb 2019 12:22:38 +0100, I wrote:
> To resolve PR89433 "Repeated use of the OpenACC 'routine' directive" at
> least for C/C++, I intend to push the attached patches in next GCC
> development stage 1 (unless that should be addressed right now, an
Hi!
To resolve PR89433 "Repeated use of the OpenACC 'routine' directive" at
least for C/C++, I intend to push the attached patches in next GCC
development stage 1 (unless that should be addressed right now, and also
on other GCC release branches?).
The corresponding Fortran
ch too large.
Is this patch OK for trunk? I bootstrapped and regtested it for x86_64
Linux with nvptx offloading. This patch is also self-contained to the
OpenACC code path.
Thanks,
Cesar
[OpenACC] Repeated use of the OpenACC routine directive
2018-XX-YY Thomas Schwinge
Cesar Philippidis
On 08/16/2016 06:05 PM, Thomas Schwinge wrote:
> On Mon, 01 Aug 2016 17:51:24 +0200, I wrote:
>> > We found that it's not correct that we currently unconditionally diagnose
>> > an error for repeated use of the OpenACC routine directive on one
>> > function/decla
On 08/16/2016 06:05 PM, Thomas Schwinge wrote:
> commit bffb0ee6c0a83b8c85cd919e1172086b51fdc452
> Author: tschwinge
> Date: Wed Aug 17 00:55:02 2016 +
>
> Repeated use of the C/C++ OpenACC routine directive
>
> gcc/
> * omp-low.c (verify_oacc_routine_clauses): Change
Hi!
On Mon, 01 Aug 2016 17:51:24 +0200, I wrote:
> We found that it's not correct that we currently unconditionally diagnose
> an error for repeated use of the OpenACC routine directive on one
> function/declaration. (For reference, it is also permissible for an
> "ordi
Hi!
We found that it's not correct that we currently unconditionally diagnose
an error for repeated use of the OpenACC routine directive on one
function/declaration. (For reference, it is also permissible for an
"ordinary" function to have several declarations plus a definition, a
