<div dir="ltr">Hi,<br><br>Thank you very much for your response.<br><br>I have encountered other problems :<br><br>1- I have coupled in the boilerplate/ for my backend ==> but test results are FAIL (out of memory !!!)<br>
2- I have generate a cairo trace for my application (Browser OWB), but when I use the cairo-perf-trace, I have this error :<br><i>[ # ] backend test min(s) median(s) stddev. count<br>[ 0] sahgfx Error during replay, line 5: invalid value (typically too big) for the size of the input (surface, pattern, etc.)<br>
[ 0] image Error during replay, line 5: invalid value (typically too big) for the size of the input (surface, pattern, etc.)</i><br><br>there is my <b>app.trace</b> file :<br><br><i>%!CairoScript - middleware<br>
%*** Warning CairoScript is still a new tracing format, and is subject to change.<br>dict<br> /type /sahgfx set<br> surface dup /s0 exch def </i><==== the problem is in this line 5<i><br>dict<br> /type /sahgfx set<br>
surface dup /s1 exch def<br>exch dup /s0 exch def<br>context % c0<br>exch dup /s1 exch def<br>context % c1<br>s1 context % c2<br>s1 context % c3<br>s1 context % c4<br>s1 context % c5<br>s1 context % c6<br>0 0 1280 720 rectangle</i><br>
<br><br>Thanks,<br><br>Best Regards,<br>Aymen CHEHAIDER<br><br><br><div class="gmail_quote">2009/10/13 Chris Wilson <span dir="ltr"><<a href="mailto:chris@chris-wilson.co.uk" target="_blank">chris@chris-wilson.co.uk</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Excerpts from aymen chehaider's message of Tue Oct 13 12:13:37 +0100 2009:<br>
<div>> I have developped a new backend for Cairo 1.9.2. *(Embedded environment)*<br>
><br>
> I want to know, how can I test perfs of this new backend ???<br>
><br>
> How can I use cairo-trace and cairo-perf-trace for this backend ?<br>
<br>
</div>First I presume that you have coupled in the boilerplate/ for your<br>
backend and are satisfied with the results from the test suite.<br>
<div><br>
> I have tried to use cairo-trace : *cairo-trace --profile my_application*<br>
> the result in the file is : *% Unknown object of type cairo_surface_t, trace<br>
</div>> is incomplete.*<br>
<br>
Indeed, it means that util/cairo-trace/trace.c does not have the<br>
appropriate hook for backend surface constructor. Simply add the<br>
relevant function wrappers by doing a copy'n'paste from one of the other<br>
backends.<br>
<br>
But recording new traces is not strictly relevant for performance<br>
testing, since you can just use the existing traces from cairo-traces.git<br>
with cairo-perf-trace. The trick here is that cairo-perf-trace uses a<br>
default value of FALSE for target_is_measurable(), so you need to add<br>
your surface type to that switch. And the same for the micro-benchmark<br>
suite, called cairo-perf for 1.9.2. And whilst we're on that subject,<br>
beware the interface changes that are in master.<br>
<br>
Hope this helps, and you have fun with cairo. Please do share any<br>
experiences you gained whilst developing a novel backend -- especially<br>
if they may help shape the internal interfaces both for easing<br>
maintenance and improving performance.<br>
-ickle<br>
<font color="#888888">--<br>
Chris Wilson, Intel Open Source Technology Centre<br>
_______________________________________________<br>
cairo mailing list<br>
<a href="mailto:cairo@cairographics.org" target="_blank">cairo@cairographics.org</a><br>
<a href="http://lists.cairographics.org/mailman/listinfo/cairo" target="_blank">http://lists.cairographics.org/mailman/listinfo/cairo</a><br>
</font></blockquote></div><br></div>