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/109610] [14 regression] gcc.target/powerpc/dform-3.c fails after r14-172-g0368d169492017
Date: Fri, 26 May 2023 01:46:44 +0000	[thread overview]
Message-ID: <bug-109610-4-GO9z7reooj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109610-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109610

--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>:

https://gcc.gnu.org/g:4fb66b2329319e9b47e89200d613b6f741a114fc

commit r14-1252-g4fb66b2329319e9b47e89200d613b6f741a114fc
Author: liuhongt <hongtao.liu@intel.com>
Date:   Tue May 16 10:36:16 2023 +0800

    Only use NO_REGS in cost calculation when !hard_regno_mode_ok for
GENERAL_REGS and mode.

    r14-172-g0368d169492017 replaces GENERAL_REGS with NO_REGS in cost
    calculation when the preferred register class are not known yet.
    It regressed powerpc PR109610 and PR109858, it looks too aggressive to use
    NO_REGS when mode can be allocated with GENERAL_REGS.
    The patch takes a step back, still use GENERAL_REGS when
    hard_regno_mode_ok for mode and GENERAL_REGS, otherwise uses NO_REGS.

    gcc/ChangeLog:

            PR target/109610
            PR target/109858
            * ira-costs.cc (scan_one_insn): Only use NO_REGS in cost
            calculation when !hard_regno_mode_ok for GENERAL_REGS and
            mode, otherwise still use GENERAL_REGS.

  parent reply	other threads:[~2023-05-26  1:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 19:45 [Bug target/109610] New: [14 regression] gcc.target/powerpc/dform-3.c fails after seurer at gcc dot gnu.org
2023-04-25  2:59 ` [Bug target/109610] [14 regression] gcc.target/powerpc/dform-3.c fails after r14-172-g0368d169492017 crazylht at gmail dot com
2023-04-25  6:31 ` rguenth at gcc dot gnu.org
2023-04-25  9:15 ` crazylht at gmail dot com
2023-04-25  9:31 ` crazylht at gmail dot com
2023-04-26  3:14 ` crazylht at gmail dot com
2023-04-26  6:41 ` crazylht at gmail dot com
2023-04-26 14:15 ` rsandifo at gcc dot gnu.org
2023-04-27  1:36 ` crazylht at gmail dot com
2023-04-27 16:22 ` bergner at gcc dot gnu.org
2023-05-06  5:46 ` crazylht at gmail dot com
2023-05-15  8:39 ` segher at gcc dot gnu.org
2023-05-15  8:40 ` segher at gcc dot gnu.org
2023-05-17  6:05 ` linkw at gcc dot gnu.org
2023-05-26  1:46 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-26  1:47 ` crazylht at gmail dot com
2023-06-02 22:56 ` bergner at gcc dot gnu.org
2023-06-06 19:44 ` seurer 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-109610-4-GO9z7reooj@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).