public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Meissner <meissner@linux.vnet.ibm.com>
To: Michael Meissner <meissner@linux.vnet.ibm.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>,
	       Segher Boessenkool <segher@kernel.crashing.org>,
	       David Edelsohn <dje.gcc@gmail.com>,
	       Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Subject: Re: [RFC Patch], PowerPC memory support pre-gcc9, patch #1
Date: Fri, 16 Mar 2018 23:31:00 -0000	[thread overview]
Message-ID: <20180316230118.GA27077@ibm-tiger.the-meissners.org> (raw)
In-Reply-To: <20180314225408.GA3365@ibm-tiger.the-meissners.org>

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

In patch #4, I mentioned that the spec 2006 benchmark 'tonto' generated
different with the patches applied.  I tracked it down, and it was due to the
call I inserted in rs6000_debug_reg_print to update the conditional register
usage seemed to set the Altivec registers VS0..VS19 to call_used instead of
call_saved.  Since I no longer need to set the conditional register usage with
-mdebug=reg, it is simpler to just delete it.

2018-03-16  Michael Meissner  <meissner@linux.vnet.ibm.com>

	* config/rs6000/rs6000.c (rs6000_debug_reg_print): Eliminate call
	to rs6000_conditional_register_usage.

-- 
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meissner@linux.vnet.ibm.com, phone: +1 (978) 899-4797

[-- Attachment #2: ext-addr.patch05b --]
[-- Type: text/plain, Size: 846 bytes --]

Index: gcc/config/rs6000/rs6000.c
===================================================================
--- gcc/config/rs6000/rs6000.c	(revision 258576)
+++ gcc/config/rs6000/rs6000.c	(working copy)
@@ -1314,7 +1314,6 @@ static bool rs6000_debug_can_change_mode
 						reg_class_t);
 static bool rs6000_save_toc_in_prologue_p (void);
 static rtx rs6000_internal_arg_pointer (void);
-static void rs6000_conditional_register_usage (void);
 
 rtx (*rs6000_legitimize_reload_address_ptr) (rtx, machine_mode, int, int,
 					     int, int *)
@@ -2144,10 +2143,6 @@ rs6000_debug_reg_print (int first_regno,
 {
   int r, m;
 
-  /* Insure the conditional registers are up to date when printing the debug
-     information.  */
-  rs6000_conditional_register_usage ();
-
   for (r = first_regno; r <= last_regno; ++r)
     {
       const char *comma = "";

  parent reply	other threads:[~2018-03-16 23:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 23:01 Michael Meissner
2018-03-15 17:09 ` [RFC Patch], PowerPC memory support pre-gcc9, patch #2 Michael Meissner
2018-03-20 13:32   ` Segher Boessenkool
2018-03-20 20:27     ` Michael Meissner
2018-03-15 23:33 ` [RFC Patch], PowerPC memory support pre-gcc9, patch #3 Michael Meissner
2018-03-16 17:27 ` [RFC Patch], PowerPC memory support pre-gcc9, patch #4 Michael Meissner
2018-03-20 16:21   ` Segher Boessenkool
2018-03-16 23:31 ` Michael Meissner [this message]
2018-03-20 16:31   ` [RFC Patch], PowerPC memory support pre-gcc9, patch #1 Segher Boessenkool
2018-03-20 13:04 ` Segher Boessenkool
2018-03-20 20:35   ` 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=20180316230118.GA27077@ibm-tiger.the-meissners.org \
    --to=meissner@linux.vnet.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=segher@kernel.crashing.org \
    --cc=wschmidt@linux.vnet.ibm.com \
    /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).