Possible narrowing conversion build fix for Compositor API example.

ppapi/examples/compositor/compositor.cc

Index: ppapi/examples/compositor/compositor.cc
diff --git a/ppapi/examples/compositor/compositor.cc b/ppapi/examples/compositor/compositor.cc
index d437bc84b77aa894aafa3d744986be980d43a7fc..360bfba9a08ee48343dd3037803419ffb78f9539 100644
--- a/ppapi/examples/compositor/compositor.cc
+++ b/ppapi/examples/compositor/compositor.cc
@@ -309,8 +309,8 @@ void DemoInstance::Paint(int32_t result, int32_t frame) {
     float x = frame % 800;
     float y = 200 - 200 * factor_sin;
     const float transform[16] = {
-      fabs(factor_sin) + 0.2f, 0.0f, 0.0f, 0.0f,
-      0.0f, fabs(factor_sin) + 0.2f, 0.0f, 0.0f,
+      fabsf(factor_sin) + 0.2f, 0.0f, 0.0f, 0.0f,
+      0.0f, fabsf(factor_sin) + 0.2f, 0.0f, 0.0f,

[dmichael (off chromium), 2014/06/17 16:16:00]

factor_sin is a float, and fabs is supposed to have an overload for float...
http://www.cplusplus.com/reference/cmath/fabs/
(see also 26.5p6 in C++03, 26.8p9 in C++11).

This seems to me like a bug GCC 4.9's C++11 support. We also don't yet build
Chromium in C++11 mode, so I'd be surprised if you didn't run in to other
problems.

You might consider making a small reproducer and filing a bug with GCC.

       0.0f, 0.0f, 1.0f, 0.0f,
          x,    y, 0.0f, 1.0f,
     };