public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/106730] [OpenMP][valid since 5.0] ICE in install_var_field, at omp-low.cc:797 for 'map(alloc:var) map(to:var)' (more than once in map clause)
Date: Wed, 24 Aug 2022 06:55:09 +0000	[thread overview]
Message-ID: <bug-106730-4-wAEi45lPh3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106730-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[OpenMP] ICE in             |[OpenMP][valid since 5.0]
                   |install_var_field, at       |ICE in install_var_field,
                   |omp-low.cc:797              |at omp-low.cc:797 for
                   |                            |'map(alloc:var)
                   |                            |map(to:var)' (more than
                   |                            |once in map clause)

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Okay – that's the
  ‘member’ appears more than once in map clauses
issue

For C/C++, there is this error – for Fortran not:
  error: ‘member’ appears more than once in map clauses
(same for 'a' and 'scalar') using the C testcase at
https://github.com/SOLLVE/sollve_vv/blob/master/tests/5.0/target/test_target_mapping_before_alloc.c
for the C/C++ testcase.

I think one pending patch was addressing on this.
Indeed, using devel/omp/gcc-12 (OG12), it compiles + runs for Fortran -
but still fails for C/C++ with the "more than once" error.

I think it is part of the following patch set:
* [PATCH 00/16] OpenMP: lvalues in "map" clauses and struct handling rework
   https://gcc.gnu.org/pipermail/gcc-patches/2021-December/586600.html
   and January + February updates (search for metadirective)
+ patch review end of May, e.g.
   https://gcc.gnu.org/pipermail/gcc-patches/2022-May/595762.html (+ 4 more
emails)

      reply	other threads:[~2022-08-24  6:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  6:45 [Bug fortran/106730] New: [OpenMP] ICE in install_var_field, at omp-low.cc:797 burnus at gcc dot gnu.org
2022-08-24  6:55 ` burnus at gcc dot gnu.org [this message]

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-106730-4-wAEi45lPh3@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).