Hi!

I've been removing mempcpy uses from libquadmath and replacing them with
memcpy + increment, but apparently missed removing one letter in one case.
Without a mempcpy prototype on targets that don't have mempcpy apparently
gcc just warns, but optimizes it into memcpy anyway, so no big harm was
done.

Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk,
queued for 4.6.1.

2011-03-25  Jakub Jelinek  <ja...@redhat.com>

        * printf/printf_fp.c (__quadmath_printf_fp): Use memcpy instead of
        mempcpy.

--- libquadmath/printf/printf_fp.c.jj   2011-02-17 10:10:01.000000000 +0100
+++ libquadmath/printf/printf_fp.c      2011-03-25 17:36:51.000000000 +0100
@@ -1197,7 +1197,7 @@ __quadmath_printf_fp (struct __quadmath_
            if (*copywc == decimalwc)
              memcpy (cp, decimal, decimal_len), cp += decimal_len;
            else if (*copywc == thousands_sepwc)
-             mempcpy (cp, thousands_sep, thousands_sep_len), cp += 
thousands_sep_len;
+             memcpy (cp, thousands_sep, thousands_sep_len), cp += 
thousands_sep_len;
            else
              *cp++ = (char) *copywc;
        }

        Jakub

Reply via email to