Lines Matching refs:queries

128     Timer queries use query objects to track the amount of time needed to
132     Timer queries are associated with query objects.  The command
172     timer queries.  The timer is started or stopped when the effects from all
197     that object is marked available. QueryCounterANGLE timer queries can be
221     TIMESTAMP_ANGLE for timer queries.
231     For timer queries (TIME_ELAPSED_ANGLE and TIMESTAMP_ANGLE), if the number
256     that if any query object returns a result available of TRUE, all queries
262     If multiple queries are issued on the same target and id prior to 
264     from the last query issued.  The results from any queries before the
349         GLint queries[N];
351         // timer queries can contain more than 32 bits of data, so always
356         glGenQueriesANGLE(N, queries);
359         glBeginQueryANGLE(GL_TIME_ELAPSED_ANGLE, queries[0]);
370         glBeginQueryANGLE(GL_TIME_ELAPSED_ANGLE, queries[N-1]);
380             glGetQueryObjectivANGLE(queries[N-1], GL_QUERY_RESULT_AVAILABLE_ANGLE, &available);
385             glGetQueryObjectui64vANGLE(queries[i], GL_QUERY_RESULT_ANGLE, &timeElapsed);
401         GLint queries[N+1];
403         // timer queries can contain more than 32 bits of data, so always
408         glGenQueriesANGLE(N+1, queries);
411         glQueryCounterANGLE(queries[0], GL_TIMESTAMP_ANGLE);
417         glQueryCounterANGLE(queries[N-1], GL_TIMESTAMP_ANGLE);
423         glQueryCounterANGLE(queries[N], GL_TIMESTAMP_ANGLE);
427             glGetQueryObjectivANGLE(queries[N], GL_QUERY_RESULT_AVAILABLE_ANGLE, &available);
432             glGetQueryObjectui64vANGLE(queries[i], GL_QUERY_RESULT_ANGLE, &timeStart);
433             glGetQueryObjectui64vANGLE(queries[i+1], GL_QUERY_RESULT_ANGLE, &timeEnd);
459     (3) What should be the minimum number of counter bits for timer queries?
484     timer queries or multiple queries of other types simultaneously.  An
491     types of queries, but not at the same time.
494     implementation -- not having to deal with queries with different result
545         TIME_ELAPSED and TIMESTAMP queries?
549    used it is possible there is a slight discrepancy when comparing queries
552    is unlikely to affect real applications since comparing the two queries is