On Fri, Jul 22, 2016 at 03:51:31PM -0400, Michael Meissner wrote: > In working on the vector extracts, I noticed that the function > altivec_resolve_overloaded_builtin has two strings that span more than one > line. This confuses the diff -p command, as it thinks modified code after the > long line is in another function. > > This patch fixes the formatting. I did a bootstrap and make check, and there > were no regressions. Is it ok to change into the trunk?
Does that work for gettext? Okay for trunk if so, thanks! Segher > /* vec_lvsl and vec_lvsr are deprecated for use with LE element order. */ > if (fcode == ALTIVEC_BUILTIN_VEC_LVSL && !VECTOR_ELT_ORDER_BIG) > - warning (OPT_Wdeprecated, "vec_lvsl is deprecated for little endian; use > \ > -assignment for unaligned loads and stores"); > + warning (OPT_Wdeprecated, > + "vec_lvsl is deprecated for little endian; use " > + "assignment for unaligned loads and stores"); > else if (fcode == ALTIVEC_BUILTIN_VEC_LVSR && !VECTOR_ELT_ORDER_BIG) > - warning (OPT_Wdeprecated, "vec_lvsr is deprecated for little endian; use > \ > -assignment for unaligned loads and stores"); > + warning (OPT_Wdeprecated, > + "vec_lvsr is deprecated for little endian; use " > + "assignment for unaligned loads and stores");
