public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/100902] pointer attachment issues
Date: Thu, 17 Jun 2021 05:59:14 +0000	[thread overview]
Message-ID: <bug-100902-4-uBprF5TtOy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100902-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:132d3e9d57a522792e300d4c8a91e9d1b8ef5577

commit r11-8588-g132d3e9d57a522792e300d4c8a91e9d1b8ef5577
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Sun Jun 6 19:37:06 2021 +0200

    openmp: Call c_omp_adjust_map_clauses even for combined target [PR100902]

    When looking at in_reduction support for target, I've noticed that
    c_omp_adjust_map_clauses is not called for the combined target case.

    The following patch fixes it.

    Unfortunately, there are other issues.

    One is (also mentioned in the PR) that currently the pointer attachment
    stuff seems to be clause ordering dependent (the standard says that clause
    ordering on the same construct does not matter), the baz and qux cases
    in the PR are rejected while when swapped it is accepted.
    Note, the order of clauses in GCC really is treated as insignificant
    initially and only later on the compiler can adjust the ordering (e.g. when
    we sort map clauses based on what they refer to etc.) and in particular,
    clauses from parsing is reverse of the order in user code, while
    c_omp_split_clauses performed for combined/composite constructs typically
    reverses that ordering, i.e. makes it follow the user code ordering.

    And another one is I'm slightly afraid c_omp_adjust_map_clauses might
    misbehave in templates, though haven't tried to verify it with testcases.
    When processing_template_decl, the non-dependent clauses will be handled
    usually the same as when not in a template, but dependent clauses aren't
    processed or only limited processing is done there, and rest is deferred
    till later.  From quick skimming of c_omp_adjust_map_clauses, it seems
    it might not be very happy about non-processed map clauses that might
    still have the TREE_LIST representation of array sections, or might
    not have finalized decls or base decls etc.
    So, for this I wonder if cp_parser_omp_target (and other cp/parser.c
    callers of c_omp_adjust_map_clauses) shouldn't call it only
    if (!processing_template_decl) - perhaps you could add
    cp_omp_adjust_map_clauses wrapper that would be
    if (!processing_template_decl)
      c_omp_adjust_map_clauses (...);
    - and call c_omp_adjust_map_clauses from within pt.c after the clauses
    are tsubsted and finish_omp_clauses is called again.

    2021-06-06  Jakub Jelinek  <jakub@redhat.com>

            PR c/100902
            * c-parser.c (c_parser_omp_target): Call c_omp_adjust_map_clauses
            even when target is combined with other constructs.

            * parser.c (cp_parser_omp_target): Call c_omp_adjust_map_clauses
            even when target is combined with other constructs.

            * c-c++-common/gomp/pr100902-1.c: New test.

    (cherry picked from commit 7fa4db39b6bcd207bd2bffff52023ff6b155bd15)

  parent reply	other threads:[~2021-06-17  5:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 11:12 [Bug c/100902] New: " jakub at gcc dot gnu.org
2021-06-04 12:46 ` [Bug c/100902] " jakub at gcc dot gnu.org
2021-06-06 17:37 ` cvs-commit at gcc dot gnu.org
2021-06-17  5:59 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-07  7:37 ` jakub at gcc dot gnu.org

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=bug-100902-4-uBprF5TtOy@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).