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/99728] code pessimization when using wrapper classes around SIMD types Date: Wed, 07 Jul 2021 11:49:55 +0000 [thread overview] Message-ID: <bug-99728-4-6eAKYQbEU2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99728-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99728 --- Comment #15 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:9f34b780b0461ec7b2b2defe96e44ab616ea2aa3 commit r12-2097-g9f34b780b0461ec7b2b2defe96e44ab616ea2aa3 Author: Richard Biener <rguenther@suse.de> Date: Wed Jul 7 11:41:03 2021 +0200 tree-optimization/99728 - improve LIM for loops with aggregate copies This improves LIM by recording aggregate copies for disambiguation purposes instead of as UNANALYZABLE_MEM which will prevent any invariant or store motion across it. This allows four of the six references in the loop of the testcase to be promoted. 2021-07-07 Richard Biener <rguenther@suse.de> PR tree-optimization/99728 * tree-ssa-loop-im.c (gather_mem_refs_stmt): Record aggregate copies. (mem_refs_may_alias_p): Add assert we handled aggregate copies elsewhere. (sm_seq_valid_bb): Give up when running into aggregate copies. (ref_indep_loop_p): Handle aggregate copies as never being invariant themselves but allow other refs to be disambiguated against them. (can_sm_ref_p): Do not try to apply store-motion to aggregate copies. * g++.dg/opt/pr99728.C: New testcase.
next prev parent reply other threads:[~2021-07-07 11:49 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-23 13:22 [Bug c++/99728] New: " martin@mpa-garching.mpg.de 2021-03-23 13:23 ` [Bug c++/99728] " martin@mpa-garching.mpg.de 2021-03-23 13:50 ` martin@mpa-garching.mpg.de 2021-03-23 13:56 ` amonakov at gcc dot gnu.org 2021-03-23 14:08 ` kretz at kde dot org 2021-03-23 14:28 ` martin@mpa-garching.mpg.de 2021-03-23 14:32 ` kretz at kde dot org 2021-03-23 14:36 ` martin@mpa-garching.mpg.de 2021-03-23 15:00 ` redi at gcc dot gnu.org 2021-03-24 8:52 ` [Bug tree-optimization/99728] " rguenth at gcc dot gnu.org 2021-03-24 9:15 ` kretz at kde dot org 2021-03-24 9:26 ` rguenther at suse dot de 2021-07-02 8:27 ` martin@mpa-garching.mpg.de 2021-07-02 9:52 ` rguenth at gcc dot gnu.org 2021-07-02 9:52 ` rguenth at gcc dot gnu.org 2021-07-02 10:53 ` rguenth at gcc dot gnu.org 2021-07-02 11:55 ` rguenth at gcc dot gnu.org 2021-07-07 11:49 ` cvs-commit at gcc dot gnu.org [this message] 2021-07-07 12:09 ` rguenth at gcc dot gnu.org 2021-07-07 13:59 ` rguenth at gcc dot gnu.org 2021-07-14 11:37 ` rguenth at gcc dot gnu.org 2021-07-14 13:04 ` 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-99728-4-6eAKYQbEU2@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).