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/102330] [12 Regression] ICE in expand_gimple_stmt_1, at cfgexpand.c:3932 since r12-980-g29a2f51806c
Date: Fri, 04 Feb 2022 12:06:56 +0000	[thread overview]
Message-ID: <bug-102330-4-wZ0FUgmgyr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102330-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Of course exceptions would be vars that certainly don't appear in the IL yet,
what I wrote about are vars that may appear there already.
Generally, vars should be marked as addressable before gimplification and
gimplification will then take the addressability into consideration, it is
wrong to mark vars as addressable in the middle of gimplification if they could
be already referenced earlier in the IL.  And similarly in omp-low.cc we
perform regimplifications and so stuff is fixable there too, but it needs to
know it should fix it up.

  parent reply	other threads:[~2022-02-04 12:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 17:27 [Bug fortran/102330] New: [12 Regression] ICE in expand_gimple_stmt_1, at cfgexpand.c:3932 gscfq@t-online.de
2021-09-15  8:00 ` [Bug fortran/102330] " rguenth at gcc dot gnu.org
2021-09-15  8:00 ` rguenth at gcc dot gnu.org
2021-09-15  8:01 ` rguenth at gcc dot gnu.org
2021-09-15  8:50 ` [Bug fortran/102330] [12 Regression] ICE in expand_gimple_stmt_1, at cfgexpand.c:3932 since r12-1139-gf6bf436d9ab907d0 marxin at gcc dot gnu.org
2021-09-15  9:04 ` jakub at gcc dot gnu.org
2021-09-15 10:27 ` tschwinge at gcc dot gnu.org
2021-09-15 10:32 ` [Bug fortran/102330] [12 Regression] ICE in expand_gimple_stmt_1, at cfgexpand.c:3932 since r12-980-g29a2f51806c burnus at gcc dot gnu.org
2021-09-15 10:41 ` jakub at gcc dot gnu.org
2022-01-17 13:30 ` rguenth at gcc dot gnu.org
2022-01-17 16:15 ` tschwinge at gcc dot gnu.org
2022-02-04 11:46 ` tschwinge at gcc dot gnu.org
2022-02-04 12:03 ` jakub at gcc dot gnu.org
2022-02-04 12:06 ` jakub at gcc dot gnu.org [this message]
2022-02-11 13:42 ` tschwinge at gcc dot gnu.org
2022-03-10 11:07 ` cvs-commit at gcc dot gnu.org
2022-03-10 11:07 ` cvs-commit at gcc dot gnu.org
2022-03-10 11:31 ` [Bug middle-end/102330] " tschwinge 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-102330-4-wZ0FUgmgyr@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).