From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id DBD5E3848400; Fri,  4 Jun 2021 11:12:56 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DBD5E3848400
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/100902] New: pointer attachment issues
Date: Fri, 04 Jun 2021 11:12:56 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-100902-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jun 2021 11:12:57 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100902

            Bug ID: 100902
           Summary: pointer attachment issues
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jakub at gcc dot gnu.org
  Target Milestone: ---

On:

void
foo (int *ptr)
{
  #pragma omp target map (ptr, ptr[:4])
  #pragma omp parallel master
  ptr[0] =3D 1;
}

void
bar (int *ptr)
{
  #pragma omp target parallel map (ptr[:4], ptr)
  #pragma omp master
  ptr[0] =3D 1;
}

foo is compiled fine, but bar ICEs because c_omp_adjust_map_clauses isn't
called
on the combined constructs.

Another bug is that
void
baz (int *ptr)
{
  #pragma omp target map (ptr[:4], ptr)
  #pragma omp parallel master
  ptr[0] =3D 1;
}

void
qux (int *ptr)
{
  #pragma omp target parallel map (ptr, ptr[:4])
  #pragma omp master
  ptr[0] =3D 1;
}

is rejected by both C and C++ pointers twice with
=E2=80=98ptr=E2=80=99 appears both in data and map clauses
The user ordering of clauses (which is reversed for the non-combined cases =
in
the implementation) should not matter.

I'll deal with the bar issue for now.=