From: Nick Clifton <nickc@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: RX: Fix thinkos in previous tidy up
Date: Fri, 13 May 2011 11:31:00 -0000 [thread overview]
Message-ID: <m31v03uenm.fsf@redhat.com> (raw)
Hi Guys,
When I applied my RX tidy up patch yesterday I forgot to rebuild the
toolchain and thus missed a couple of thinkos with my rename of the
rx_legitimate_constant_p function. I therefore applying the patch
below to fix this problem.
Cheers
Nick
gcc/ChangeLog
2011-05-13 Nick Clifton <nickc@redhat.com>
* config/rx/rx.md (mov expander): Fix use of
rx_legitimate_constant_p.
* config/rx/rx-protos.h (rx_legitimate_constant_p): Rename
prototype.
Index: gcc/config/rx/rx-protos.h
===================================================================
--- gcc/config/rx/rx-protos.h (revision 173723)
+++ gcc/config/rx/rx-protos.h (working copy)
@@ -31,7 +31,7 @@
extern void rx_emit_stack_pushm (rtx *);
extern void rx_expand_epilogue (bool);
extern char * rx_gen_move_template (rtx *, bool);
-extern bool rx_legitimate_constant_p (enum machine_mode, rtx);
+extern bool rx_is_legitimate_constant (enum machine_mode, rtx);
extern bool rx_is_restricted_memory_address (rtx,
enum machine_mode);
extern bool rx_match_ccmode (rtx, enum machine_mode);
Index: gcc/config/rx/rx.md
===================================================================
--- gcc/config/rx/rx.md (revision 173723)
+++ gcc/config/rx/rx.md (working copy)
@@ -556,7 +556,7 @@
if (MEM_P (operand0) && MEM_P (operand1))
operands[1] = copy_to_mode_reg (<register_modes:MODE>mode, operand1);
if (CONST_INT_P (operand1)
- && ! rx_legitimate_constant_p (<register_modes:MODE>mode, operand1))
+ && ! rx_is_legitimate_constant (<register_modes:MODE>mode, operand1))
FAIL;
}
)
reply other threads:[~2011-05-13 9:34 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=m31v03uenm.fsf@redhat.com \
--to=nickc@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).