sungmg/mutter-performance-source
1
0
Fork 0
Code Activity

journal: Don't push and pop the framebuffer when flushing

Browse source 
In theory none of the journal flushing code should be using anything
that relies on the global framebuffer stack because it should all be
using the new 2.0-style API which explicitly mentions the target
framebuffer. Eventually we want to get rid of the framebuffer stack so
we might as well remove the push and pop now.

Reviewed-by: Robert Bragg <robert@linux.intel.com>
This commit is contained in:
Neil Roberts 2012-03-16 17:31:03 +00:00
parent ff48f3b174
commit a5f2f0fe2d
1 changed files with 0 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
cogl/cogl-journal.c
View file

@ -1381,8 +1381,6 @@ _cogl_journal_flush (CoglJournal *journal)
* that the timer isn't started recursively. */
COGL_TIMER_START (_cogl_uprof_context, flush_timer);
cogl_push_framebuffer (journal->framebuffer);
if (G_UNLIKELY (COGL_DEBUG_ENABLED (COGL_DEBUG_BATCHING)))
g_print ("BATCHING: journal len = %d\n", journal->entries->len);
@ -1465,8 +1463,6 @@ _cogl_journal_flush (CoglJournal *journal)
_cogl_journal_discard (journal);
cogl_pop_framebuffer ();
COGL_TIMER_STOP (_cogl_uprof_context, flush_timer);
}