[cairo-bugs] [Bug 4846] Performance problems for GTK+/Cairo on MacOS X

[bugzilla-daemon at freedesktop.org]

Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=4846          
     




------- Additional Comments From cworth at cworth.org  2005-10-26 17:11 -------
(In reply to comment #16)
> For the record, it was a bug in the compiler,

Ah, at least one mystery solved then.

> Now for the topic of rounding. I would say first you should define exactly
your definition of rounding 
> which is appropriate for your problem domain. It should be specified
unambiguously.

Yes. That is good, sound advice. We've got a large pass of "robustification" to
be done with the upcoming rewrite of the tessellator. This rounding will also
be an important part of that.

[Snipped many good insights and comments which will be useful---thanks!]

> Cairo is already critical infrastructure, please make it fail-proof and
idiot-proof (that's me :-))

Hey, I'm one of the biggest idiots involved with this project. (And I think
I can back that claim up with bugzilla comments.)

> With my unfortunate experience that started this thread, I would be cautious.

Caution, at least, is something I can be good at. You may notice that long
before the optimization patch I linked to above, we've had a patch proposed
for making this function a macro. I've been waiting for better proof that
we know we have implemented what we want before making a macro out of it.

> And, btw, thank you Carl et al for this brilliant piece of software.

For what it's worth, you're quite welcome. I'll pass the "brilliant" portion
of your thanks on to Keith. It's all his ideas originally.

Thank you for your contributions, (and I'm glad you've got cairo and GTK+
running at more reasonable speeds now).

-Carl          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.