From: Richard Sandiford <richard.sandiford@arm.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] Use target-insns.def for reload_load_address
Date: Tue, 28 Jul 2015 22:10:00 -0000 [thread overview]
Message-ID: <87mvygm325.fsf@e105548-lin.cambridge.arm.com> (raw)
Bootstrapped & regression-tested on x86_64-linux-gnu and aarch64-linux-gnu.
Also tested via config-list.mk. Committed as preapproved.
Thanks,
Richard
gcc/
* target-insns.def (reload_load_address): New targetm instruction
pattern.
* reload1.c (gen_reload): Use it instead of HAVE_*/gen_* interface.
Index: gcc/target-insns.def
===================================================================
--- gcc/target-insns.def 2015-06-28 12:29:34.245633312 +0100
+++ gcc/target-insns.def 2015-06-28 12:30:58.298088971 +0100
@@ -61,6 +61,7 @@ DEF_TARGET_INSN (probe_stack, (rtx x0))
DEF_TARGET_INSN (probe_stack_address, (rtx x0))
DEF_TARGET_INSN (prologue, (void))
DEF_TARGET_INSN (ptr_extend, (rtx x0, rtx x1))
+DEF_TARGET_INSN (reload_load_address, (rtx x0, rtx x1))
DEF_TARGET_INSN (restore_stack_block, (rtx x0, rtx x1))
DEF_TARGET_INSN (restore_stack_function, (rtx x0, rtx x1))
DEF_TARGET_INSN (restore_stack_nonlocal, (rtx x0, rtx x1))
Index: gcc/reload1.c
===================================================================
--- gcc/reload1.c 2015-06-27 17:11:38.224086135 +0100
+++ gcc/reload1.c 2015-06-28 12:29:34.245633312 +0100
@@ -8813,10 +8813,8 @@ gen_reload (rtx out, rtx in, int opnum,
mark_jump_label (in, tem, 0);
}
-#ifdef HAVE_reload_load_address
- else if (HAVE_reload_load_address)
- emit_insn (gen_reload_load_address (out, in));
-#endif
+ else if (targetm.have_reload_load_address ())
+ emit_insn (targetm.gen_reload_load_address (out, in));
/* Otherwise, just write (set OUT IN) and hope for the best. */
else
reply other threads:[~2015-07-28 20:37 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=87mvygm325.fsf@e105548-lin.cambridge.arm.com \
--to=richard.sandiford@arm.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).