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 fortran/103039] [12 Regression] Segfault with openmp block within a select type block since r12-1016-g0e3b3b77e13cac76
Date: Fri, 18 Mar 2022 16:40:55 +0000	[thread overview]
Message-ID: <bug-103039-4-KxSJqyFOb6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103039-4@http.gcc.gnu.org/bugzilla/>

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

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

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

commit r12-7709-gc133bdfa9e7d9225510d00dbb7270cc052e4e4ee
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Fri Mar 18 17:40:22 2022 +0100

    Fortran/OpenMP: Fix privatization of associated names

    gfc_omp_predetermined_sharing cases the associate-name pointer variable
    to be OMP_CLAUSE_DEFAULT_FIRSTPRIVATE, which is fine. However, the
associated
    selector is shared. Thus, the target of associate-name pointer should not
get
    copied. (It was before but because of gfc_omp_privatize_by_reference
returning
    false, the selector was not only wrongly copied but this was also not done
    properly.)

    gcc/fortran/ChangeLog:

            PR fortran/103039
            * trans-openmp.cc (gfc_omp_clause_copy_ctor, gfc_omp_clause_dtor):
            Only privatize pointer for associate names.

    libgomp/ChangeLog:

            PR fortran/103039
            * testsuite/libgomp.fortran/associate4.f90: New test.

  parent reply	other threads:[~2022-03-18 16:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02  9:08 [Bug fortran/103039] New: Segfault with openmp block within a select type block mscfd at gmx dot net
2021-11-02  9:12 ` [Bug fortran/103039] " mscfd at gmx dot net
2021-11-02  9:20 ` marxin at gcc dot gnu.org
2021-11-02 10:26 ` [Bug fortran/103039] Segfault with openmp block within a select type block since r12-1016-g0e3b3b77e13cac76 mscfd at gmx dot net
2022-01-25  8:28 ` mscfd at gmx dot net
2022-01-25  9:16 ` [Bug fortran/103039] [12 Regression] " jakub at gcc dot gnu.org
2022-03-09 14:27 ` rguenth at gcc dot gnu.org
2022-03-17 16:41 ` jakub at gcc dot gnu.org
2022-03-18 12:29 ` burnus at gcc dot gnu.org
2022-03-18 12:37 ` jakub at gcc dot gnu.org
2022-03-18 13:50 ` cvs-commit at gcc dot gnu.org
2022-03-18 16:40 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-18 16:42 ` burnus at gcc dot gnu.org
2022-03-21 11:59 ` mscfd at gmx dot net

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-103039-4-KxSJqyFOb6@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).