public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108422] [13 Regression] ICE: base pointer cycle detected since r13-2661-gb57abd072dd319a7
Date: Mon, 20 Feb 2023 10:02:55 +0000 [thread overview]
Message-ID: <bug-108422-4-4sQwpiJmLP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108422-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108422
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Created attachment 54491
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54491&action=edit
Testcase - compile with 'g++ -fopenmp' + run
(In reply to Tobias Burnus from comment #3)
> --- a/gcc/gimplify.cc
> +++ b/gcc/gimplify.cc
> @@ -9643 +9643 @@ omp_tsort_mapping_groups_1 (omp_mapping_group ***outlist,
> - if (innerp && *innerp != grp)
> + if (innerp && *innerp != grp && (*innerp)->mark != PERMANENT)
While COMPILING WORKS and the expected nested-target warning is printed,
it FAILS at RUNTIME (on a system not configured for offloading) with a
segfault.
That's related to the warning:
test.cc:20:13: warning: '__closure' is used uninitialized [-Wuninitialized]
which appears at the location of the outer 'omp target (parallel)'.
Note: without inner target construct (reverse offload), the program runs fine.
(Independent of the one-line patch.)
next prev parent reply other threads:[~2023-02-20 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 17:49 [Bug c++/108422] New: [13 Regression] ICE: base pointer cycle detected gscfq@t-online.de
2023-01-17 7:04 ` [Bug c++/108422] " rguenth at gcc dot gnu.org
2023-01-17 13:29 ` [Bug c++/108422] [13 Regression] ICE: base pointer cycle detected since r13-2661-gb57abd072dd319a7 marxin at gcc dot gnu.org
2023-02-20 9:26 ` burnus at gcc dot gnu.org
2023-02-20 9:45 ` burnus at gcc dot gnu.org
2023-02-20 10:02 ` burnus at gcc dot gnu.org [this message]
2023-02-21 13:05 ` rguenth at gcc dot gnu.org
2023-02-21 17:43 ` burnus at gcc dot gnu.org
2023-04-26 6:57 ` [Bug c++/108422] [13/14 " rguenth at gcc dot gnu.org
2023-07-27 9:25 ` rguenth at gcc dot gnu.org
2024-05-21 9:13 ` [Bug c++/108422] [13/14/15 " 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-108422-4-4sQwpiJmLP@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).