Hi!
On Thu, 4 Aug 2016 11:03:25 -0600, Jeff Law wrote:
> On 07/27/2016 09:17 AM, Thomas Schwinge wrote:
> > I found that for a lot of OpenACC (and potentially also OpenMP) clauses
> > (in C/C++ front ends; didn't look at Fortran), we use wrong location
> > information. The problem is that
> > c_
Hi!
On Wed, 27 Jul 2016 17:17:49 +0200, I wrote:
> I found that for a lot of OpenACC (and potentially also OpenMP) clauses
> (in C/C++ front ends; didn't look at Fortran), we use wrong location
> information. The problem is [...]
Haven't been able yet to allocate the time to incorporate David's
On 07/27/2016 09:17 AM, Thomas Schwinge wrote:
Hi!
I found that for a lot of OpenACC (and potentially also OpenMP) clauses
(in C/C++ front ends; didn't look at Fortran), we use wrong location
information. The problem is that
c_parser_oacc_all_clauses/c_parser_omp_all_clauses calls
cp_parser_omp
On Wed, 2016-07-27 at 17:17 +0200, Thomas Schwinge wrote:
> Hi!
>
> I found that for a lot of OpenACC (and potentially also OpenMP)
> clauses
> (in C/C++ front ends; didn't look at Fortran), we use wrong location
> information. The problem is that
> c_parser_oacc_all_clauses/c_parser_omp_all_clau
