| Message ID | CACUk7=UTZ+6GGFKEBKifHcWzsNS0t3++9eoy40_J_U+kgp3GCg@mail.gmail.com |
|---|---|
| State | Accepted |
| Headers | show |
Index: gcc/config/arm/vfp.md =================================================================== --- gcc/config/arm/vfp.md (revision 182037) +++ gcc/config/arm/vfp.md (working copy) @@ -1171,7 +1171,7 @@ "@ vmov.f32\\t%0, %1\;vcvt.f64.<FCVTI32typename>\\t%P0, %P0, %v2 vmov.f32\\t%0, %1\;vcvt.f64.<FCVTI32typename>\\t%P0, %P0, %v2 - vmov.f64\\t%0, %1, %1\; vcvt.f64.<FCVTI32typename>\\t%P0, %P0, %v2" + vmov.f64\\t%P0, %1, %1\;vcvt.f64.<FCVTI32typename>\\t%P0, %P0, %v2" [(set_attr "predicable" "no") (set_attr "type" "f_cvt") (set_attr "length" "8")]
Hi, There was a missing %P with the last commit for the fixed to floating point conversion idioms which caused ffmpeg builds to break by accidentally putting out a vmov.f64 s0, r0, r0 instead of the vmov.f64 d0, r0, r0. Tested with a simple testcase and made sure that the output obtained is sane. Committed as obvious. cheers Ramana 2011-12-06 Ramana Radhakrishnan <ramana.radhakrishnan@linaro.org> * config/arm/vfp.md (*combine_vcvt_f64_<FCVTI32typename>): Fix formatting character for vmov.f64 case.