ambiguous insn in altivec

David Edelsohn dje@watson.ibm.com
Tue Jan 8 12:41:00 GMT 2002


>>>>> Aldy Hernandez writes:

Aldy> is there a reason for the second insn?  you added this.

Aldy> (define_insn "altivec_vspltisw"
Aldy> [(set (match_operand:V4SI 0 "register_operand" "=v")
Aldy> (unspec:V4SI [(match_operand:QI 1 "immediate_operand" "i")] 141))]
Aldy> "TARGET_ALTIVEC"
Aldy> "vspltisw %0, %1"
Aldy> [(set_attr "type" "vecsimple")])

Aldy> (define_insn ""
Aldy> [(set (match_operand:V4SF 0 "register_operand" "=v")
Aldy> (unspec:V4SF [(match_operand:QI 1 "immediate_operand" "i")] 142))]
Aldy> "TARGET_ALTIVEC"
Aldy> "vspltisw %0, %1"
Aldy> [(set_attr "type" "vecsimple")])

	One is SImode and one is SFmode.

David



More information about the Gcc mailing list