On Fri, Feb 3, 2012 at 3:59 PM, Fu, Chao-Ying wrote:
> Liu [pro...@gmail.com] wrote:
>
>> OK, I get.
>> But, sorry, my mips64dspr2 patch has be done...
>> Should I summit it?
>
> I just wonder what version of the MIPS64 DSP/DSPr2 spec that you
> implemented. Do you have a target CPU that has th
Liu [pro...@gmail.com] wrote:
> OK, I get.
> But, sorry, my mips64dspr2 patch has be done...
> Should I summit it?
I just wonder what version of the MIPS64 DSP/DSPr2 spec that you implemented.
Do you have a target CPU that has these MIPS64 DSP/DSPr2 instructions? My
concern is that the late
On Fri, Feb 3, 2012 at 12:40 PM, Fu, Chao-Ying wrote:
> Richard Sandiford [rdsandif...@googlemail.com] wrote:
>
>> This pattern maps directly to __builtin_mips_prepend, which is defined
>> to take and return an SI type, so :SI is the correct choice here.
>>
>> I agree it might be nice to have a fu
Richard Sandiford [rdsandif...@googlemail.com] wrote:
> This pattern maps directly to __builtin_mips_prepend, which is defined
> to take and return an SI type, so :SI is the correct choice here.
>
> I agree it might be nice to have a function that operates on 64-bit
> values for 64-bit targets tho
Liu writes:
> diff --git a/gcc/config/mips/mips-dspr2.md b/gcc/config/mips/mips-dspr2.md
> index 5ae902f..6853b9d 100644
> --- a/gcc/config/mips/mips-dspr2.md
> +++ b/gcc/config/mips/mips-dspr2.md
> @@ -345,7 +345,7 @@
> (set_attr "mode" "SI")])
>
> (define_insn "mips_prepend"
> - [(set (
diff --git a/gcc/config/mips/mips-dspr2.md
b/gcc/config/mips/mips-dspr2.mdindex 5ae902f..6853b9d 100644---
a/gcc/config/mips/mips-dspr2.md+++ b/gcc/config/mips/mips-dspr2.md@@
-345,7 +345,7 @@ (set_attr "mode""SI")]) (define_insn
"mips_prepend"- [(set (match_operand:SI 0 "register_operand"