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 c/99322] [11 Regression] ICE in change_scope, at final.c:1480
Date: Fri, 05 Mar 2021 16:41:08 +0000	[thread overview]
Message-ID: <bug-99322-4-XFn9gmBN6t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99322-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
void bar (void *);
void
foo (void)
{
  bar (&&lab);
  #pragma omp parallel
  for (;;)
    ;
  lab:;
}
ICEs likely since r0-88143-gb357f682db35f4431e3011e7486a0ac865686e3e
Not really sure what to do if we find unreachable blocks with labels that need
to be preserved, we need to figure out where to place them exactly.
As the problematic pass is only the cfg pass (if flag_openmp || flag_openacc ||
flag_openmp_simd), I wonder if we e.g. shouldn't keep bb_to_omp_idx valid
across the cleanup_tree_cfg and if non-NULL, use that for the forced label from
unreachable blocks placement.

  parent reply	other threads:[~2021-03-05 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 17:02 [Bug c/99322] New: " gscfq@t-online.de
2021-03-01 19:10 ` [Bug c/99322] " pinskia at gcc dot gnu.org
2021-03-02  9:42 ` marxin at gcc dot gnu.org
2021-03-05 14:52 ` jakub at gcc dot gnu.org
2021-03-05 16:41 ` jakub at gcc dot gnu.org [this message]
2021-03-05 16:59 ` [Bug middle-end/99322] " jakub at gcc dot gnu.org
2021-03-05 20:59 ` cvs-commit at gcc dot gnu.org
2021-03-05 21:01 ` jakub 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-99322-4-XFn9gmBN6t@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).