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, 25 Oct 2021 12:09:39 +0000 [thread overview] Message-ID: <bug-100382-4-M5ps98v6fW@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 #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:7518e4c2f0758daac5d650d400565cf49ac3c8c5 commit r12-4661-g7518e4c2f0758daac5d650d400565cf49ac3c8c5 Author: Andrew Pinski <apinski@marvell.com> Date: Sat Oct 23 19:24:43 2021 +0000 Fix PR 102908: wrongly removing null pointer loads Just like PR 100382, here we have a DCE removing a null pointer load which is needed still. In this case, execute_fixup_cfg removes a store (correctly) and then removes the null load (incorrectly) due to not checking stmt_unremovable_because_of_non_call_eh_p. This patch adds the check in the similar way as the patch to fix PR 100382 did. gcc/ChangeLog: * tree-ssa-dce.c (simple_dce_from_worklist): Check stmt_unremovable_because_of_non_call_eh_p also before removing the statement.
prev parent reply other threads:[~2021-10-25 12:09 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 2021-05-03 10:12 ` jakub at gcc dot gnu.org 2021-10-25 12:09 ` cvs-commit at gcc dot gnu.org [this message]
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-M5ps98v6fW@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).