This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[PATCH 1/9] gensupport: Fix define_subst operand renumbering.
- From: Andreas Krebbel <krebbel at linux dot vnet dot ibm dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Thu, 14 Jan 2016 17:33:26 +0100
- Subject: [PATCH 1/9] gensupport: Fix define_subst operand renumbering.
- Authentication-results: sourceware.org; auth=none
- References: <1452789254-12603-1-git-send-email-krebbel at linux dot vnet dot ibm dot com>
When processing substitutions the operands are renumbered. To find a
free operand number the array used_operands_numbers is used to record
the operand numbers already in use. Currently this array is used to
assign new numbers *before* all the RTXes in the vector have been
processed.
I did run into problems with this for insns where a match_dup occurred
in a later (use ...) operand referring to an earlier operand
(e.g. s390.md "setmem_long").
The patch splits the loop doing the processing into two in order to
have all the operand numbers recorded already when assigning new
numbers.
Bootstrapped and regtested on s390, s390x, and x86_64.
Ok for mainline?
Bye,
-Andreas-
gcc/ChangeLog:
2016-01-14 Andreas Krebbel <krebbel@linux.vnet.ibm.com>
* gensupport.c (process_substs_on_one_elem): Split loop to
complete mark_operands_used_in_match_dup on all expressions in the
vector first.
(adjust_operands_numbers): Inline into process_substs_on_one_elem
and remove function.
---
gcc/gensupport.c | 41 +++++++++++++++++++++--------------------
1 file changed, 21 insertions(+), 20 deletions(-)
diff --git a/gcc/gensupport.c b/gcc/gensupport.c
index 596b885..8ace425 100644
--- a/gcc/gensupport.c
+++ b/gcc/gensupport.c
@@ -126,7 +126,10 @@ static const char * duplicate_each_alternative (const char * str, int n_dup);
typedef const char * (*constraints_handler_t) (const char *, int);
static rtx alter_constraints (rtx, int, constraints_handler_t);
-static rtx adjust_operands_numbers (rtx);
+
+static void mark_operands_used_in_match_dup (rtx);
+static void renumerate_operands_in_pattern (rtx);
+
static rtx replace_duplicating_operands_in_pattern (rtx);
/* Make a version of gen_rtx_CONST_INT so that GEN_INT can be used in
@@ -1843,7 +1846,15 @@ process_substs_on_one_elem (struct queue_elem *elem,
subst_pattern = alter_constraints (subst_pattern, alternatives,
duplicate_each_alternative);
- subst_pattern = adjust_operands_numbers (subst_pattern);
+ mark_operands_used_in_match_dup (subst_pattern);
+ RTVEC_ELT (subst_pattern_vec, j) = subst_pattern;
+ }
+
+ for (j = 0; j < XVECLEN (subst_elem->data, 3); j++)
+ {
+ subst_pattern = RTVEC_ELT (subst_pattern_vec, j);
+
+ renumerate_operands_in_pattern (subst_pattern);
/* Substitute match_dup and match_op_dup in the new pattern and
duplicate constraints. */
@@ -1856,7 +1867,6 @@ process_substs_on_one_elem (struct queue_elem *elem,
if (GET_CODE (elem->data) == DEFINE_EXPAND)
remove_constraints (subst_pattern);
- RTVEC_ELT (subst_pattern_vec, j) = subst_pattern;
}
XVEC (elem->data, 1) = subst_pattern_vec;
@@ -1976,6 +1986,14 @@ find_first_unused_number_of_operand ()
It visits all expressions in PATTERN and assigns not-occupied
operand indexes to MATCH_OPERANDs and MATCH_OPERATORs of this
PATTERN. */
+/* If output pattern of define_subst contains MATCH_DUP, then this
+ expression would be replaced with the pattern, matched with
+ MATCH_OPERAND from input pattern. This pattern could contain any
+ number of MATCH_OPERANDs, MATCH_OPERATORs etc., so it's possible
+ that a MATCH_OPERAND from output_pattern (if any) would have the
+ same number, as MATCH_OPERAND from copied pattern. To avoid such
+ indexes overlapping, we assign new indexes to MATCH_OPERANDs,
+ laying in the output pattern outside of MATCH_DUPs. */
static void
renumerate_operands_in_pattern (rtx pattern)
{
@@ -2010,23 +2028,6 @@ renumerate_operands_in_pattern (rtx pattern)
}
}
-/* If output pattern of define_subst contains MATCH_DUP, then this
- expression would be replaced with the pattern, matched with
- MATCH_OPERAND from input pattern. This pattern could contain any
- number of MATCH_OPERANDs, MATCH_OPERATORs etc., so it's possible
- that a MATCH_OPERAND from output_pattern (if any) would have the
- same number, as MATCH_OPERAND from copied pattern. To avoid such
- indexes overlapping, we assign new indexes to MATCH_OPERANDs,
- laying in the output pattern outside of MATCH_DUPs. */
-static rtx
-adjust_operands_numbers (rtx pattern)
-{
- mark_operands_used_in_match_dup (pattern);
-
- renumerate_operands_in_pattern (pattern);
-
- return pattern;
-}
/* Generate RTL expression
(match_dup OPNO)
--
1.9.1