From: tbsaunde+gcc@tbsaunde.org
To: gcc-patches@gcc.gnu.org
Subject: [PATCH 06/13] make some functions in lra-constraints.c take rtx_insn *
Date: Sat, 02 May 2015 21:02:00 -0000 [thread overview]
Message-ID: <1430600503-14069-7-git-send-email-tbsaunde+gcc@tbsaunde.org> (raw)
In-Reply-To: <1430600503-14069-1-git-send-email-tbsaunde+gcc@tbsaunde.org>
From: Trevor Saunders <tbsaunde+gcc@tbsaunde.org>
gcc/ChangeLog:
2015-05-02 Trevor Saunders <tbsaunde+gcc@tbsaunde.org>
* lra-constraints.c: Change type of some arguments to rtx_insn *.
---
gcc/ChangeLog | 4 ++++
gcc/lra-constraints.c | 4 ++--
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 6807ec5..17ad3df 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,5 +1,9 @@
2015-05-02 Trevor Saunders <tbsaunde+gcc@tbsaunde.org>
+ * lra-constraints.c: Change type of some arguments to rtx_insn *.
+
+2015-05-02 Trevor Saunders <tbsaunde+gcc@tbsaunde.org>
+
* regcprop.c (kill_autoinc_value): Change type of argument to
rtx_insn *.
diff --git a/gcc/lra-constraints.c b/gcc/lra-constraints.c
index 791f7de..5c4c2f2 100644
--- a/gcc/lra-constraints.c
+++ b/gcc/lra-constraints.c
@@ -4141,7 +4141,7 @@ contains_deleted_insn_p (rtx_insn_list *list)
/* Return true if X contains a pseudo dying in INSN. */
static bool
-dead_pseudo_p (rtx x, rtx insn)
+dead_pseudo_p (rtx x, rtx_insn *insn)
{
int i, j;
const char *fmt;
@@ -4544,7 +4544,7 @@ setup_next_usage_insn (int regno, rtx insn, int reloads_num, bool after_p)
optional debug insns finished by a non-debug insn using REGNO.
RELOADS_NUM is current number of reload insns processed so far. */
static void
-add_next_usage_insn (int regno, rtx insn, int reloads_num)
+add_next_usage_insn (int regno, rtx_insn *insn, int reloads_num)
{
rtx next_usage_insns;
--
2.4.0
next prev parent reply other threads:[~2015-05-02 21:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 21:02 [PATCH 00/13] further rtx_insn *ification tbsaunde+gcc
2015-05-02 21:02 ` [PATCH 10/13] make fp_setter_insn take a rtx_insn * tbsaunde+gcc
2015-05-02 21:02 ` [PATCH 13/13] make emit_partition_copy return " tbsaunde+gcc
2015-05-02 21:02 ` [PATCH 09/13] make validate_replace_src_group take " tbsaunde+gcc
2015-05-02 21:02 ` [PATCH 05/13] kill_autoinc_value can " tbsaunde+gcc
2015-05-02 21:02 ` [PATCH 07/13] make some functions in config/ " tbsaunde+gcc
2015-05-02 21:02 ` [PATCH 04/13] recog_data::insn can be " tbsaunde+gcc
2015-05-02 21:02 ` tbsaunde+gcc [this message]
2015-05-02 21:02 ` [PATCH 01/13] change local vars to " tbsaunde+gcc
2015-05-02 21:02 ` [PATCH 11/13] type reg_equiv_init as rtx_insn_list tbsaunde+gcc
2015-05-02 21:02 ` [PATCH 12/13] make set_return_jump_label take an rtx_insn * tbsaunde+gcc
2015-05-02 21:02 ` [PATCH 08/13] make several functions in the scheduler take " tbsaunde+gcc
2015-05-02 21:02 ` [PATCH 02/13] df_set_note can take a " tbsaunde+gcc
2015-05-02 21:02 ` [PATCH 03/13] add_cfi_insn can be " tbsaunde+gcc
2015-05-04 17:16 ` [PATCH 00/13] further rtx_insn *ification Jeff Law
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=1430600503-14069-7-git-send-email-tbsaunde+gcc@tbsaunde.org \
--to=tbsaunde+gcc@tbsaunde.org \
--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).