Add CC software renderer.

cc/CCResourceProvider.cpp

Index: cc/CCResourceProvider.cpp
diff --git a/cc/CCResourceProvider.cpp b/cc/CCResourceProvider.cpp
index 3cfc5f96ebea38f9569f30e635235612d3440d20..b72d454ba6188209ea36e303e6ad98115bd75986 100644
--- a/cc/CCResourceProvider.cpp
+++ b/cc/CCResourceProvider.cpp
@@ -342,9 +342,7 @@ bool CCResourceProvider::initialize()
     WebGraphicsContext3D* context3d = m_context->context3D();
     if (!context3d) {
         m_maxTextureSize = INT_MAX;

[danakj, 2012/09/19 18:35:14]

If you do something like

if (textureSize > m_maxTextureSize)

and they are both ints, and m_maxTextureSize == INT_MAX, isn't that going to
just going to be always true?

If this is going to be INT_MAX should m_maxTextureSize be an unsigned (this
would force other places to be unsigned in order to compare)?

It reminds me of all the overflow issues caused by INT_MAX stuff in the subpixel
layout code. The checks we have in place for max texture size would be no-ops in
this case.

[aelias_OOO_until_Jul13, 2012/09/19 19:58:27]

(textureSize > m_maxTextureSize) would always be false, as desired.  That said
you have a point that INT_MAX has some insane properties, for example if we ever
add it to any positive number.  I mainly wanted to avoid a magic number.  I
guess we could go with INT_MAX / 2 or 100000000?

[danakj, 2012/09/19 20:06:18]

er.. false. yes. I'd prefer a magic number, yeh. Maybe something based on
INT_MAX more than an independent constant, so INT_MAX/2.

-
-        // FIXME: Implement this path for software compositing.
-        return false;
+        return true;
     }
     if (!context3d->makeContextCurrent())
         return false;