public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/109858] [14 Regression] r14-172 caused some SPEC2017 bmk to degrade on Power
Date: Wed, 17 May 2023 01:25:31 +0000 [thread overview]
Message-ID: <bug-109858-4-jKnLI7EkyL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109858-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109858
--- Comment #8 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Segher Boessenkool from comment #7)
> > The patch will still use GENERAL_REGS when hard_regno_mode_ok for mode and
> > GENERAL_REGS(which is the case in PR109610), hope it can also fix this
> > regression.
>
> That sounds more reasonable. But, why use any heuristics like this? Can't
> you
> just look at the actual costs of using mem and regs?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109610#c2
next prev parent reply other threads:[~2023-05-17 1:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 2:06 [Bug rtl-optimization/109858] New: " linkw at gcc dot gnu.org
2023-05-15 2:24 ` [Bug rtl-optimization/109858] " pinskia at gcc dot gnu.org
2023-05-15 2:25 ` pinskia at gcc dot gnu.org
2023-05-15 7:43 ` [Bug rtl-optimization/109858] [14 Regression] " crazylht at gmail dot com
2023-05-15 9:40 ` linkw at gcc dot gnu.org
2023-05-16 2:50 ` crazylht at gmail dot com
2023-05-16 2:53 ` crazylht at gmail dot com
2023-05-16 3:08 ` linkw at gcc dot gnu.org
2023-05-16 15:17 ` segher at gcc dot gnu.org
2023-05-17 1:25 ` crazylht at gmail dot com [this message]
2023-05-17 5:21 ` linkw at gcc dot gnu.org
2023-05-17 14:48 ` segher at gcc dot gnu.org
2023-05-26 1:46 ` cvs-commit at gcc dot gnu.org
2023-06-20 10:35 ` linkw 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-109858-4-jKnLI7EkyL@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).