public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/100382] [12 Regression] go.test/test/fixedbugs/issue16095.go hang since r12-248 Date: Mon, 03 May 2021 10:04:03 +0000 [thread overview] Message-ID: <bug-100382-4-BBPPdCNOCM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100382-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100382 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:80bbb7ff83d81544b09820428bdd7db9f50fe362 commit r12-378-g80bbb7ff83d81544b09820428bdd7db9f50fe362 Author: Jakub Jelinek <jakub@redhat.com> Date: Mon May 3 12:03:02 2021 +0200 tree-ssa-dse: Fix up go.test/test/fixedbugs/issue16095.go miscompilation [PR100382] The new DCE code inside of tree DSE removes in -fnon-call-exceptions go code a load from NULL pointer the testcase relies on throwing an exception and so the test hangs. The following patch just repeats a check that e.g. tree-ssa-dce.c uses to prevent this. 2021-05-03 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/100382 * tree-ssa-dse.c: Include tree-eh.h. (dse_dom_walker::before_dom_children): Don't remove stmts if stmt_unremovable_because_of_non_call_eh_p is true.
next prev parent reply other threads:[~2021-05-03 10:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-02 14:54 [Bug tree-optimization/100382] New: " jakub at gcc dot gnu.org 2021-05-02 14:54 ` [Bug tree-optimization/100382] " jakub at gcc dot gnu.org 2021-05-02 17:46 ` jakub at gcc dot gnu.org 2021-05-03 6:51 ` rguenth at gcc dot gnu.org 2021-05-03 7:13 ` rguenth at gcc dot gnu.org 2021-05-03 10:04 ` cvs-commit at gcc dot gnu.org [this message] 2021-05-03 10:12 ` jakub at gcc dot gnu.org 2021-10-25 12:09 ` cvs-commit 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-100382-4-BBPPdCNOCM@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).