I found it difficult to grasp which functions from generic.c are
actually called (and, following up on that, how much time is spent in
each of them). So I decided to add some profiling #defines to generic.c
which you can find in the attached patch (profiling only for x86
architecture so far).
The output looks something like this:
*funcs++ = Sop_is_Aop;
*funcs++ = Dacc_is_Aacc;
*funcs++ = Sop_PFI_to_Dacc[pindex];
*funcs++ = Sacc_is_NULL;
*funcs++ = Xacc_is_Aacc;
*funcs++ = Xacc_blend[state->dst_blend - 1];
*funcs++ = Cacc_add_to_Dacc;
*funcs++ = Sacc_is_Aacc;
*funcs++ = Dop_is_Aop;
*funcs++ = Sacc_to_Dop_PFI[pindex];
*funcs = NULL;
profile: Sop_rgb32_to_Dacc took 154368 cycles
profile: Xacc_blend_invsrcalpha took 4642 cycles
profile: Cacc_add_to_Dacc_noMMX took 2591 cycles
profile: Sacc_to_Dop_rgb32 took 4841 cycles
Felix
-- No attachments (even text) are allowed --
-- Type: text/plain
--
Info: To unsubscribe send a mail to [EMAIL PROTECTED] with
"unsubscribe directfb-dev" as subject.
