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 middle-end/109849] suboptimal code for vector walking loop Date: Tue, 23 May 2023 09:57:57 +0000 [thread overview] Message-ID: <bug-109849-4-Je6h9SRJ0D@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109849-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109849 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:9e2017ae6ac788d3e36999bb0f0d20ea0f62c20e commit r14-1127-g9e2017ae6ac788d3e36999bb0f0d20ea0f62c20e Author: Richard Biener <rguenther@suse.de> Date: Thu May 18 13:52:29 2023 +0200 tree-optimization/109849 - missed code hoisting The following fixes code hoisting to properly consider ANTIC_OUT instead of ANTIC_IN. That's a bit expensive to re-compute but since we no longer iterate we're doing this only once per BB which should be acceptable. This avoids missing hoistings to the end of blocks where something in the block clobbers the hoisted value. PR tree-optimization/109849 * tree-ssa-pre.cc (do_hoist_insertion): Compute ANTIC_OUT and use that to determine what to hoist. * gcc.dg/tree-ssa/ssa-hoist-8.c: New testcase.
next prev parent reply other threads:[~2023-05-23 9:57 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-13 22:26 [Bug middle-end/109849] New: " hubicka at gcc dot gnu.org 2023-05-13 22:32 ` [Bug middle-end/109849] " pinskia at gcc dot gnu.org 2023-05-13 22:40 ` pinskia at gcc dot gnu.org 2023-05-14 5:57 ` amonakov at gcc dot gnu.org 2023-05-14 9:58 ` hubicka at ucw dot cz 2023-05-14 10:01 ` hubicka at ucw dot cz 2023-05-15 6:56 ` rguenth at gcc dot gnu.org 2023-05-17 14:53 ` hubicka at gcc dot gnu.org 2023-05-17 20:36 ` rguenth at gcc dot gnu.org 2023-05-18 9:35 ` hubicka at gcc dot gnu.org 2023-05-18 11:54 ` rguenth at gcc dot gnu.org 2023-05-18 13:00 ` hubicka at gcc dot gnu.org 2023-05-23 9:57 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-23 10:10 ` rguenth at gcc dot gnu.org 2023-05-24 11:19 ` cvs-commit at gcc dot gnu.org 2023-06-16 14:20 ` hubicka at gcc dot gnu.org 2023-06-18 16:59 ` cvs-commit at gcc dot gnu.org 2023-06-19 16:28 ` cvs-commit at gcc dot gnu.org 2023-06-26 16:30 ` cvs-commit at gcc dot gnu.org 2023-06-28 9:47 ` cvs-commit at gcc dot gnu.org 2023-06-29 20:46 ` cvs-commit at gcc dot gnu.org 2023-06-30 14:28 ` cvs-commit at gcc dot gnu.org 2023-11-19 15:25 ` hubicka at gcc dot gnu.org 2023-11-21 14:17 ` cvs-commit at gcc dot gnu.org 2023-11-21 15:12 ` hubicka at gcc dot gnu.org 2023-11-24 16:35 ` cvs-commit at gcc dot gnu.org 2023-11-24 17:00 ` cvs-commit at gcc dot gnu.org 2023-11-24 17:00 ` jamborm at gcc dot gnu.org 2023-11-27 14:39 ` rguenth at gcc dot gnu.org 2023-11-28 9:33 ` redi at gcc dot gnu.org 2023-11-28 10:32 ` jamborm at gcc dot gnu.org 2023-11-28 12:41 ` redi at gcc dot gnu.org 2023-11-28 13:29 ` redi at gcc dot gnu.org 2023-11-28 15:29 ` redi at gcc dot gnu.org 2023-11-28 22:21 ` redi at gcc dot gnu.org 2023-11-29 12:27 ` hubicka at ucw dot cz 2023-11-29 15:25 ` cvs-commit at gcc dot gnu.org 2024-01-03 17:41 ` jamborm 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-109849-4-Je6h9SRJ0D@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).