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 tree-optimization/97000] [11 Regression][nvptx, openacc] internal compiler error: in nvptx_find_par, at config/nvptx/nvptx.c:3293
Date: Wed, 09 Sep 2020 16:10:32 +0000 [thread overview]
Message-ID: <bug-97000-4-tUcF7fqToU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97000-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97000
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2020-09-09
Summary|[nvptx, openacc] internal |[11 Regression][nvptx,
|compiler error: in |openacc] internal compiler
|nvptx_find_par, at |error: in nvptx_find_par,
|config/nvptx/nvptx.c:3293 |at
| |config/nvptx/nvptx.c:3293
Status|UNCONFIRMED |NEW
Keywords| |ice-on-valid-code
Version|unknown |11.0
Target Milestone|--- |11.0
CC| |burnus at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Bisecting points to r11-3009-gfab77644842869adc8871e133e4c3f4c35b2b245
PR tree-optimization/96931 - clear ctrl-altering flag more aggressively
2020-09-04 Richard Biener <rguenther@suse.de>
PR tree-optimization/96931
* tree-cfgcleanup.c (cleanup_call_ctrl_altering_flag): If
there's a fallthru edge and no abnormal edge the call is
no longer control-altering.
(cleanup_control_flow_bb): Pass down the BB to
cleanup_call_ctrl_altering_flag.
@Richard: See also tentative patch in comment 2
next prev parent reply other threads:[~2020-09-09 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 14:38 [Bug tree-optimization/97000] New: [nvptx, " vries at gcc dot gnu.org
2020-09-09 14:44 ` [Bug tree-optimization/97000] " vries at gcc dot gnu.org
2020-09-09 14:45 ` vries at gcc dot gnu.org
2020-09-09 15:52 ` vries at gcc dot gnu.org
2020-09-09 16:10 ` burnus at gcc dot gnu.org [this message]
2020-09-09 16:15 ` [Bug tree-optimization/97000] [11 Regression][nvptx, " vries at gcc dot gnu.org
2020-09-09 16:32 ` vries at gcc dot gnu.org
2020-09-09 16:53 ` vries at gcc dot gnu.org
2020-09-09 17:43 ` vries at gcc dot gnu.org
2020-09-10 6:43 ` rguenth at gcc dot gnu.org
2020-09-10 11:11 ` vries at gcc dot gnu.org
2020-09-10 11:12 ` vries 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-97000-4-tUcF7fqToU@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).