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/101373] PRE hoists trapping instructions over possibly throwing calls Date: Wed, 13 Oct 2021 11:09:01 +0000 [thread overview] Message-ID: <bug-101373-4-3vV5APgxLy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101373-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101373 --- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:95a95ec274cd0ec125ce48ab002fad4e400e345b commit r10-10206-g95a95ec274cd0ec125ce48ab002fad4e400e345b Author: Richard Biener <rguenther@suse.de> Date: Tue Aug 17 08:38:35 2021 +0200 tree-optimization/101868 - avoid PRE of trapping mems across calls This backports a fix for the omission of a check of trapping mems when hoisting them across calls that might not return. This was originally done as part of a fix to handle const functions that throw properly. 2021-08-17 Richard Biener <rguenther@suse.de> PR tree-optimization/101373 PR tree-optimization/101868 * tree-ssa-pre.c (prune_clobbered_mems): Also prune trapping references when the BB may not return. * gcc.dg/lto/pr101868_0.c: New testcase. * gcc.dg/lto/pr101868_1.c: Likewise. * gcc.dg/lto/pr101868_2.c: Likewise. * gcc.dg/lto/pr101868_3.c: Likewise. (cherry picked from commit ee875b63b22e30a0dcb4b05f7532c2c416ba6cd0)
next prev parent reply other threads:[~2021-10-13 11:09 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-08 7:36 [Bug tree-optimization/101373] New: " rguenth at gcc dot gnu.org 2021-07-08 7:37 ` [Bug tree-optimization/101373] " rguenth at gcc dot gnu.org 2021-07-08 14:12 ` rguenth at gcc dot gnu.org 2021-07-09 9:28 ` ebotcazou at gcc dot gnu.org 2021-07-09 10:12 ` rguenther at suse dot de 2021-07-09 11:05 ` ebotcazou at gcc dot gnu.org 2021-07-09 11:15 ` rguenth at gcc dot gnu.org 2021-07-09 16:33 ` ebotcazou at gcc dot gnu.org 2021-07-09 17:37 ` ebotcazou at gcc dot gnu.org 2021-07-09 19:43 ` ebotcazou at gcc dot gnu.org 2021-07-10 17:13 ` rguenther at suse dot de 2021-07-10 17:14 ` rguenther at suse dot de 2021-07-12 7:28 ` ebotcazou at gcc dot gnu.org 2021-07-12 8:30 ` rguenth at gcc dot gnu.org 2021-07-12 8:38 ` ebotcazou at gcc dot gnu.org 2021-07-12 14:47 ` cvs-commit at gcc dot gnu.org 2021-07-12 14:48 ` rguenth at gcc dot gnu.org 2021-08-17 9:21 ` cvs-commit at gcc dot gnu.org 2021-08-25 2:43 ` pinskia at gcc dot gnu.org 2021-10-13 11:09 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-08 14:07 ` cvs-commit at gcc dot gnu.org 2022-01-05 14:41 ` rguenth 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-101373-4-3vV5APgxLy@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).