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 target/109040] [13 Regression] wrong code with v16hi compare & mask on riscv64 at -O2 since r13-4907-g2e886eef7f2b5a
Date: Wed, 19 Apr 2023 09:13:54 +0000 [thread overview]
Message-ID: <bug-109040-4-Quut0TJObl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109040-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109040
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:76f44fbfea1f11e53d4b7e83f0debd029c94a1b3
commit r14-64-g76f44fbfea1f11e53d4b7e83f0debd029c94a1b3
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Apr 19 11:13:11 2023 +0200
dse: Use SUBREG_REG for copy_to_mode_reg in DSE replace_read for
WORD_REGISTER_OPERATIONS targets [PR109040]
While we've agreed this is not the right fix for the PR109040 bug,
the patch clearly improves generated code (at least on the testcase from
the
PR), so I'd like to propose this as optimization heuristics improvement
for GCC 14.
2023-04-19 Jakub Jelinek <jakub@redhat.com>
PR target/109040
* dse.cc (replace_read): If read_reg is a SUBREG of a word mode
REG, for WORD_REGISTER_OPERATIONS copy SUBREG_REG of it into
a new REG rather than the SUBREG.
prev parent reply other threads:[~2023-04-19 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 11:14 [Bug target/109040] New: [13 Regression] wrong code with v16hi compare & mask on riscv64 at -O2 zsojka at seznam dot cz
2023-03-07 9:01 ` [Bug target/109040] " rguenth at gcc dot gnu.org
2023-03-27 8:29 ` marxin at gcc dot gnu.org
2023-03-27 8:45 ` [Bug target/109040] [13 Regression] wrong code with v16hi compare & mask on riscv64 at -O2 since r13-4907-g2e886eef7f2b5a marxin at gcc dot gnu.org
2023-04-04 12:54 ` jakub at gcc dot gnu.org
2023-04-04 13:41 ` jakub at gcc dot gnu.org
2023-04-04 13:46 ` jakub at gcc dot gnu.org
2023-04-04 15:02 ` jakub at gcc dot gnu.org
2023-04-04 20:08 ` ebotcazou at gcc dot gnu.org
2023-04-05 14:17 ` law at gcc dot gnu.org
2023-04-14 7:32 ` cvs-commit at gcc dot gnu.org
2023-04-19 9:13 ` 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-109040-4-Quut0TJObl@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).