Commit 216aa5ed by zmo@google.com

Map long for-loop control variable names in shaders.

Look at TIntermLoop::traverse() in IntermTraverse.cpp, the control init part is not handled explicitly there (unlike the other two parts). It is expected hat visitLoop will cover the init part. The bug in the MapLongVariableNames is that the visitLoop doesn't do anything. This CL fixes it. BUG=171 TEST=conformance/glsl-long-variable-names.html passing. Review URL: http://codereview.appspot.com/4644045 git-svn-id: https://angleproject.googlecode.com/svn/trunk@696 736b8ea6-26fd-11df-bfd4-992fa37f6226
parent dc4b4f85
#define MAJOR_VERSION 0
#define MINOR_VERSION 0
#define BUILD_VERSION 0
#define BUILD_REVISION 695
#define BUILD_REVISION 696
#define STRINGIFY(x) #x
#define MACRO_STRINGIFY(x) STRINGIFY(x)
......
......@@ -67,13 +67,15 @@ bool MapLongVariableNames::visitSelection(Visit, TIntermSelection*)
return true;
}
bool MapLongVariableNames::visitAggregate(Visit, TIntermAggregate* node)
bool MapLongVariableNames::visitAggregate(Visit, TIntermAggregate*)
{
return true;
}
bool MapLongVariableNames::visitLoop(Visit, TIntermLoop*)
bool MapLongVariableNames::visitLoop(Visit, TIntermLoop* node)
{
if (node->getInit())
node->getInit()->traverse(this);
return true;
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment