Commit 523036d4 by Matthew Fortune Committed by Matthew Fortune

MIPS: Fix wrong use of XINT instead of INTVAL

This issue was caught with assert checking enabled but is not a
functional bug as XINT(x, 0) happens to overlay INTVAL(x) anyway.

gcc/
	* config/mips/mips.c (mips_final_prescan_insn): Fix incorrect
	XINT with INTVAL.
	(mips_final_postscan_insn): Likewise.

From-SVN: r258099
parent 71a93e81
2018-03-01 Matthew Fortune <mfortune@gmail.com>
* config/mips/mips.c (mips_final_prescan_insn): Fix incorrect
XINT with INTVAL.
(mips_final_postscan_insn): Likewise.
2018-03-01 Richard Sandiford <richard.sandiford@linaro.org> 2018-03-01 Richard Sandiford <richard.sandiford@linaro.org>
PR rtl-optimization/84528 PR rtl-optimization/84528
......
...@@ -20426,7 +20426,7 @@ mips_final_prescan_insn (rtx_insn *insn, rtx *opvec, int noperands) ...@@ -20426,7 +20426,7 @@ mips_final_prescan_insn (rtx_insn *insn, rtx *opvec, int noperands)
&& GET_CODE (PATTERN (insn)) == UNSPEC_VOLATILE && GET_CODE (PATTERN (insn)) == UNSPEC_VOLATILE
&& XINT (PATTERN (insn), 1) == UNSPEC_CONSTTABLE) && XINT (PATTERN (insn), 1) == UNSPEC_CONSTTABLE)
mips_set_text_contents_type (asm_out_file, "__pool_", mips_set_text_contents_type (asm_out_file, "__pool_",
XINT (XVECEXP (PATTERN (insn), 0, 0), 0), INTVAL (XVECEXP (PATTERN (insn), 0, 0)),
FALSE); FALSE);
if (mips_need_noat_wrapper_p (insn, opvec, noperands)) if (mips_need_noat_wrapper_p (insn, opvec, noperands))
...@@ -20450,7 +20450,7 @@ mips_final_postscan_insn (FILE *file ATTRIBUTE_UNUSED, rtx_insn *insn, ...@@ -20450,7 +20450,7 @@ mips_final_postscan_insn (FILE *file ATTRIBUTE_UNUSED, rtx_insn *insn,
&& GET_CODE (PATTERN (insn)) == UNSPEC_VOLATILE && GET_CODE (PATTERN (insn)) == UNSPEC_VOLATILE
&& XINT (PATTERN (insn), 1) == UNSPEC_CONSTTABLE_END) && XINT (PATTERN (insn), 1) == UNSPEC_CONSTTABLE_END)
mips_set_text_contents_type (asm_out_file, "__pend_", mips_set_text_contents_type (asm_out_file, "__pend_",
XINT (XVECEXP (PATTERN (insn), 0, 0), 0), INTVAL (XVECEXP (PATTERN (insn), 0, 0)),
TRUE); TRUE);
} }
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment