public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge 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-1139-gf6bf436d9ab907d0 Date: Wed, 15 Sep 2021 10:27:56 +0000 [thread overview] Message-ID: <bug-102330-4-cn3lE7zc83@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 Thomas Schwinge <tschwinge at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jules at gcc dot gnu.org, | |tschwinge at gcc dot gnu.org --- Comment #5 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #4) > Just > program p > !$omp taskloop lastprivate(i) > do i = 1, 8 > end do > !$acc parallel loop > do i = 1, 8 > end do > end > is enough to reproduce it. Confirmed. With '-fopt-info-omp-all --param=openacc-privatization=noisy' we're told: 'note: variable ‘i’ in ‘private’ clause is candidate for adjusting OpenACC privatization level', and... (In reply to Richard Biener from comment #1) > Confirmed. omp expansion seems to introudce this non-gimple code and likely > also makes 'i' not a register (for OACC): > > .data_dep.5D.4044 = .UNIQUE (OACC_PRIVATE, .data_dep.5D.4044, -1, > &iD.4045); > > but > > iD.4045 = 1 + .offset.9D.4049; > > and > > iD.4045 = 1 + 8; > > (which is also unfolded) ... indeed the ICE goes away if I force-disable 'OACC_PRIVATE' commit 29a2f51806c5b30e17a8d0e9ba7915a3c53c34ff "openacc: Add support for gang local storage allocation in shared memory [PR90115]" as follows: --- gcc/omp-low.c +++ gcc/omp-low.c @@ -10494,6 +10494,8 @@ static bool oacc_privatization_candidate_p (const location_t loc, const tree c, const tree decl) { + return false; Hmm. Julian CCed.
next prev parent reply other threads:[~2021-09-15 10:27 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 [this message] 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 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-cn3lE7zc83@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: linkBe 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).