glValidateProgramPipeline called in libary function


while debugging my code I had several callstacks inside the Power VR driver where the functions glValidateProgramPipeline and glGetProgramPipeline were called as part of the glDrawElements function and caused some cpu footprint. I do not use this functions anywhere in my code. Is this wanted driver behaviour for production code?


I have checked with the drivers guys and they do not know about this. They reckon that these new extensions are possibly from a completely different driver, a wrapper or a modified driver. This is definitely code that does not look suitable for production. Have you asked you platform supplier?




no yet, but if you say its unusual I definively will.