public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97927] gfortran: ICE in lookup_field_for_decl, at tree-nested.c:288
Date: Mon, 23 Nov 2020 18:32:21 +0000	[thread overview]
Message-ID: <bug-97927-4-NRuHHk5vzl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97927-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Can't reproduce with 20201005 10 branch or current trunk.
The 10 branch changed tree-nested.c e.g. in r10-8663, but I don't really see
any linear, lastprivate or reduction clauses in this.

  parent reply	other threads:[~2020-11-23 18:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 10:55 [Bug fortran/97927] New: " doko at debian dot org
2020-11-20 10:58 ` [Bug fortran/97927] " jakub at gcc dot gnu.org
2020-11-20 11:03 ` doko at debian dot org
2020-11-20 14:20 ` dominiq at lps dot ens.fr
2020-11-20 14:22 ` doko at debian dot org
2020-11-20 14:35 ` dominiq at lps dot ens.fr
2020-11-20 14:53 ` doko at debian dot org
2020-11-21 17:22 ` dominiq at lps dot ens.fr
2020-11-23 18:32 ` jakub at gcc dot gnu.org [this message]
2020-11-24 12:09 ` burnus at gcc dot gnu.org
2021-03-05 12:04 ` doko at debian dot org
2021-03-05 13:49 ` doko at debian dot org
2021-03-05 13:51 ` burnus at gcc dot gnu.org
2021-03-05 18:56 ` burnus at gcc dot gnu.org
2021-03-05 19:08 ` burnus at gcc dot gnu.org
2021-03-06 10:13 ` burnus at gcc dot gnu.org
2021-03-08 12:06 ` cvs-commit at gcc dot gnu.org
2021-03-15 14:44 ` cvs-commit at gcc dot gnu.org
2021-03-15 14:46 ` 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-97927-4-NRuHHk5vzl@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).