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 middle-end/108546] [11/12/13 Regression] ICE in expand_expr_real_1, at expr.cc:10910 since r10-4531-ga2c26c50310a3363
Date: Thu, 09 Mar 2023 11:10:51 +0000	[thread overview]
Message-ID: <bug-108546-4-kKrAsA5XXP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108546-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Tobias Burnus
<burnus@gcc.gnu.org>:

https://gcc.gnu.org/g:e7d995cf9bff2ca4a54b94c4a38455ebd1c2883e

commit r11-10565-ge7d995cf9bff2ca4a54b94c4a38455ebd1c2883e
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Wed Mar 1 13:53:09 2023 +0100

    OpenMP/Fortran: Fix handling of optional is_device_ptr + bind(C) [PR108546]

    For is_device_ptr, optional checks should only be done before calling
    libgomp, afterwards they are NULL either because of absent or, by
    chance, because it is unallocated or unassociated (for
pointers/allocatables).

    Additionally, it fixes an issue with explicit mapping for 'type(c_ptr)'.

            PR middle-end/108546

    gcc/fortran/ChangeLog:

            * trans-openmp.c (gfc_trans_omp_clauses): Fix mapping of
            type(C_ptr) variables.

    gcc/ChangeLog:

            * omp-low.c (lower_omp_target): Remove optional handling
            on the receiver side, i.e. inside target (data), for
            use_device_ptr.

    libgomp/ChangeLog:

            * testsuite/libgomp.fortran/is_device_ptr-3.f90: New test.
            * testsuite/libgomp.fortran/use_device_ptr-optional-4.f90: New
test.

    (cherry picked from commit 96ff97ff6574666a5509ae9fa596e7f2b6ad4f88)

  parent reply	other threads:[~2023-03-09 11:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 17:52 [Bug fortran/108546] New: [11/12/13 Regression] ICE in expand_expr_real_1, at expr.cc:10910 gscfq@t-online.de
2023-01-26  7:44 ` [Bug fortran/108546] " rguenth at gcc dot gnu.org
2023-01-26  9:43 ` [Bug fortran/108546] [11/12/13 Regression] ICE in expand_expr_real_1, at expr.cc:10910 since r10-4531-ga2c26c50310a3363 marxin at gcc dot gnu.org
2023-02-21 12:56 ` [Bug middle-end/108546] " rguenth at gcc dot gnu.org
2023-03-01 12:53 ` cvs-commit at gcc dot gnu.org
2023-03-08 10:55 ` cvs-commit at gcc dot gnu.org
2023-03-09 11:10 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-09 11:11 ` burnus 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-108546-4-kKrAsA5XXP@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).