public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH] Fix minor fallout from output_address changes
Date: Tue, 10 Nov 2015 21:13:00 -0000	[thread overview]
Message-ID: <56425DEA.2030800@redhat.com> (raw)

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

The ft32 and moxie ports failed to build after the recent output_address 
changes.  Fixed thusly and committed to the trunk after verifying the 
moxie and ft32 ports in config-list.mk build again.

Jeff

[-- Attachment #2: P --]
[-- Type: text/plain, Size: 2127 bytes --]

commit b408dd85568c5d0c0a9673810280a8438753b60f
Author: law <law@138bc75d-0d04-0410-961f-82ee72b054a4>
Date:   Tue Nov 10 21:11:07 2015 +0000

    [PATCH] Fix minor fallout from output_address changes
    2015-11-10  Jeff Law  <law@redhat.com>
    
    	* config/ft32/ft32.c (ft32_print_operand): Supply mode to
    	call to output_address.
    	* config/moxie/moxie.c (moxie_print_operand_address): Similarly.
    	Add unnamed machine_mode argument.
    
    git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@230130 138bc75d-0d04-0410-961f-82ee72b054a4

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 2c966e7..84481ef 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,10 @@
+2015-11-10  Jeff Law  <law@redhat.com>
+
+	* config/ft32/ft32.c (ft32_print_operand): Supply mode to
+	call to output_address.
+	* config/moxie/moxie.c (moxie_print_operand_address): Similarly.
+	Add unnamed machine_mode argument.
+
 2015-11-10  Michael Meissner  <meissner@linux.vnet.ibm.com>
 
 	* config.gcc (powerpc*-*-*, rs6000*-*-*): Add power9 to hosts that
diff --git a/gcc/config/ft32/ft32.c b/gcc/config/ft32/ft32.c
index 85e5ba3..ab62061 100644
--- a/gcc/config/ft32/ft32.c
+++ b/gcc/config/ft32/ft32.c
@@ -238,7 +238,7 @@ ft32_print_operand (FILE * file, rtx x, int code)
       return;
 
     case MEM:
-      output_address (XEXP (operand, 0));
+      output_address (GET_MODE (XEXP (operand, 0)), XEXP (operand, 0));
       return;
 
     default:
diff --git a/gcc/config/moxie/moxie.c b/gcc/config/moxie/moxie.c
index a45b825..756e2f7 100644
--- a/gcc/config/moxie/moxie.c
+++ b/gcc/config/moxie/moxie.c
@@ -106,7 +106,7 @@ moxie_operand_lossage (const char *msgid, rtx op)
 /* The PRINT_OPERAND_ADDRESS worker.  */
 
 static void
-moxie_print_operand_address (FILE *file, rtx x)
+moxie_print_operand_address (FILE *file, machine_mode, rtx x)
 {
   switch (GET_CODE (x))
     {
@@ -183,7 +183,7 @@ moxie_print_operand (FILE *file, rtx x, int code)
       return;
 
     case MEM:
-      output_address (XEXP (operand, 0));
+      output_address (GET_MODE (XEXP (operand, 0)), XEXP (operand, 0));
       return;
 
     default:

                 reply	other threads:[~2015-11-10 21:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=56425DEA.2030800@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@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).