Hi!
[please do not top-post]
On Thu, 20 Apr 2023 21:13:08 +0800
"Zhu, Lipeng" wrote:
> Hi Bernhard,
>
> Thanks for your questions and suggestions.
> The rwlock could allow multiple threads to have concurrent read-only
> access to the cache/unit list, only a single writer is allowed.
right.
On Sat, Apr 22, 2023 at 08:43:53PM +0200, Mikael Morin wrote:
> >
> OK, let's go with your patch as originally submitted then.
>
Mikael, thanks for looking at the original patch and
suggested an alternative location to attempt to fix
the bug. Halrald, thanks for following up on Mikael's
suggest
Cc:ing Thomas, who knows openacc better.
There is a devel/omp/gcc-12 branch you might want to try. I don't know
how different that branch is wrt openacc.
HTH,
On Mon, 24 Apr 2023 19:39:15
+0200 Patrick Begou via Fortran wrote:
> Hi Harald
>
> as I said, it is a large, massively parallel fortr
Hi Harald
as I said, it is a large, massively parallel fortran code: more than 700
files, some with several thousands of lines. It could be difficult to
create a small reproducer but I will try if the problem is not known as
an other git branch of this code also create an internal error on
an
Hi Patrick,
I did not see any similar report in bugzilla, so could you please
open a PR and attach a self-contained reproducer? Ideally the
reproducer would be reduced to simplify the analysis for those
familiar with the status of the OpenACC implementation.
Thanks,
Harald
Am 21.04.23 um 17:13
On Sun, 23 Apr 2023 23:48:03 +0200
Harald Anlauf via Fortran wrote:
> Am 22.04.23 um 10:32 schrieb Paul Richard Thomas via Gcc-patches:
> > PR103931 - I couldn't reproduce the bug, which involves 'ambiguous c_ptr'.
> > To judge by the comments, it seems that this bug is a bit elusive.
See Haral
