public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/meissner/heads/dmf001)] Update ChangeLog.meissner.
Date: Wed, 19 Oct 2022 03:46:58 +0000 (GMT)	[thread overview]
Message-ID: <20221019034658.B90313858D3C@sourceware.org> (raw)

https://gcc.gnu.org/g:8b6fd3fee914d7031848632118f20a5fb004261c

commit 8b6fd3fee914d7031848632118f20a5fb004261c
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Tue Oct 18 23:46:39 2022 -0400

    Update ChangeLog.meissner.
    
    2022-10-18   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/
    
            * config/rs6000/rs6000.cc (rs6000_debugger_regno): Add support for DMF
            registers.

Diff:
---
 gcc/config/rs6000/rs6000.cc | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc
index 9d5d1ce1930..9b9fa75d8ba 100644
--- a/gcc/config/rs6000/rs6000.cc
+++ b/gcc/config/rs6000/rs6000.cc
@@ -22724,7 +22724,8 @@ rs6000_memory_move_cost (machine_mode mode, reg_class_t rclass,
   else if (reg_classes_intersect_p (rclass, ALTIVEC_REGS))
     ret = 4 * hard_regno_nregs (FIRST_ALTIVEC_REGNO, mode);
   else if (reg_classes_intersect_p (rclass, DMF_REGS))
-    ret = 4 + rs6000_register_move_cost (mode, rclass, VSX_REGS);
+    ret = (rs6000_dmf_register_move_cost (mode, VSX_REGS)
+	   + rs6000_memory_move_cost (mode, VSX_REGS, false));
   else
     ret = 4 + rs6000_register_move_cost (mode, rclass, GENERAL_REGS);
 
@@ -24099,6 +24100,10 @@ rs6000_debugger_regno (unsigned int regno, unsigned int format)
     return 67;
   if (regno == 64)
     return 64;
+  /* XXX: This is a guess.  The GCC register number for FIRST_DMF_REGNO is 111,
+     but the frame pointer regnum above uses that.  */
+  if (DMF_REGNO_P (regno))
+    return regno - FIRST_DMF_REGNO + 112;
 
   gcc_unreachable ();
 }

             reply	other threads:[~2022-10-19  3:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19  3:46 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-27  5:17 Michael Meissner
2022-10-27  3:37 Michael Meissner
2022-10-20  6:06 Michael Meissner
2022-10-20  4:11 Michael Meissner
2022-10-19  4:16 Michael Meissner
2022-10-19  3:53 Michael Meissner
2022-10-18 22:36 Michael Meissner
2022-10-18 22:26 Michael Meissner
2022-10-17 23:18 Michael Meissner
2022-10-15  0:12 Michael Meissner
2022-10-15  0:06 Michael Meissner
2022-10-14 17:36 Michael Meissner
2022-10-13 17:59 Michael Meissner
2022-10-12  2:33 Michael Meissner
2022-10-11 23:19 Michael Meissner
2022-10-11 16:02 Michael Meissner
2022-10-10 21:52 Michael Meissner
2022-10-10 21:52 Michael Meissner

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=20221019034658.B90313858D3C@sourceware.org \
    --to=meissner@gcc.gnu.org \
    --cc=gcc-cvs@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).