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/109046] [13 Regresion] caused by complex lower.
Date: Mon, 13 Mar 2023 08:49:29 +0000 [thread overview]
Message-ID: <bug-109046-4-E7hMmnDbd8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109046-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109046
--- Comment #2 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:eb337d28c32b1b460cc85b3c00f8418ca535c77b
commit r13-6624-geb337d28c32b1b460cc85b3c00f8418ca535c77b
Author: Richard Biener <rguenther@suse.de>
Date: Tue Mar 7 11:04:55 2023 +0100
tree-optimization/109046 - re-combine complex loads
The following addresses PR109046 by adding an optimization to forwprop
to combine a piecewise complex load to a complex load when there are
no other uses of the components. That's something useful in general and
easier to do than avoiding the splitting in complex lowering.
The testcase exercises both the manual and the complex lowering case.
PR tree-optimization/109046
* tree-ssa-forwprop.cc (pass_forwprop::execute): Combine
piecewise complex loads.
* gcc.dg/tree-ssa/forwprop-39.c: New testcase.
next prev parent reply other threads:[~2023-03-13 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 5:40 [Bug tree-optimization/109046] New: 13 regresion " crazylht at gmail dot com
2023-03-07 9:14 ` [Bug tree-optimization/109046] [13 Regresion] " rguenth at gcc dot gnu.org
2023-03-13 8:49 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-13 8:49 ` 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-109046-4-E7hMmnDbd8@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: link
Be 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).