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/102621] ICE in convert_nonlocal_reference_op, at tree-nested.c:1166 since r12-1108-g9a5de4d5af1c10a8
Date: Thu, 20 Jan 2022 21:30:59 +0000	[thread overview]
Message-ID: <bug-102621-4-xzSy8MC0l9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102621-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Sandra Loosemore <sandra@gcc.gnu.org>:

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

commit r12-6780-gd2ad748eeef0dd260f3993b8dcbffbded3240a0a
Author: Sandra Loosemore <sandra@codesourcery.com>
Date:   Thu Jan 20 13:29:48 2022 -0800

    Fortran: Fix scope for OMP AFFINITY clause iterator variables [PR103695]

    gfc_finish_var_decl was confused by the undocumented overloading of
    the proc_name field in struct gfc_namespace to contain iterator
    variables for the OpenMP AFFINITY clause, causing it to insert the
    decls in the wrong scope.  This patch adds a new distinct field to
    hold these variables.

    2022-01-20  Sandra Loosemore  <sandra@codesourcery.com>

            PR fortran/103695
            PR fortran/102621

            gcc/fortran
            * gfortran.h (struct gfc_namespace) Add omp_affinity_iterator
            field.
            * dump-parse-tree.cc (show_iterator): Use it.
            * openmp.cc (gfc_match_iterator): Likewise.
            (resolve_omp_clauses): Likewise.
            * trans-decl.cc (gfc_finish_var_decl): Likewise.
            * trans-openmp.cc (handle_iterator): Likewise.

            gcc/testsuite/
            * gfortran.dg/gomp/affinity-clause-3.f90: Adjust pattern.
            * gfortran.dg/gomp/pr102621.f90: New.
            * gfortran.dg/gomp/pr103695.f90: New.

      parent reply	other threads:[~2022-01-20 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 18:36 [Bug fortran/102621] New: [12 Regression] ICE in convert_nonlocal_reference_op, at tree-nested.c:1166 gscfq@t-online.de
2021-10-06  8:41 ` [Bug fortran/102621] " rguenth at gcc dot gnu.org
2021-10-11  8:28 ` [Bug fortran/102621] [12 Regression] ICE in convert_nonlocal_reference_op, at tree-nested.c:1166 since r12-1108-g9a5de4d5af1c10a8 marxin at gcc dot gnu.org
2022-01-20  9:23 ` [Bug fortran/102621] " rguenth at gcc dot gnu.org
2022-01-20 16:01 ` sandra at gcc dot gnu.org
2022-01-20 21:30 ` cvs-commit 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-102621-4-xzSy8MC0l9@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).