Mark private method layoutBlockFlow as inline

Source/core/rendering/RenderBlockFlow.cpp

Index: Source/core/rendering/RenderBlockFlow.cpp
diff --git a/Source/core/rendering/RenderBlockFlow.cpp b/Source/core/rendering/RenderBlockFlow.cpp
index 8370a7bc4aa3b91467243ff59d1a790b6f19c449..c90e924371983ad626d39bdc3eca9ec124489dbd 100644
--- a/Source/core/rendering/RenderBlockFlow.cpp
+++ b/Source/core/rendering/RenderBlockFlow.cpp
@@ -251,7 +251,7 @@ void RenderBlockFlow::layoutBlock(bool relayoutChildren)
     layoutBlockFlow(relayoutChildren);
 }
 
-void RenderBlockFlow::layoutBlockFlow(bool relayoutChildren, LayoutUnit pageLogicalHeight)
+inline void RenderBlockFlow::layoutBlockFlow(bool relayoutChildren, LayoutUnit pageLogicalHeight)

[Inactive, 2014/01/20 18:57:50]

Yes, looking at the original patch, it seems like the extra function call in the
layoutBlock() virtual function is the only difference that might impact
performance.
Hopefully, inlining it will fix the regression.

 {
     ASSERT(needsLayout());
     ASSERT(isInlineBlockOrInlineTable() || !isInline());