Open
Bug 542818
Opened 16 years ago
Updated 3 years ago
Avoid converting to a fixed point representation in cairo
Categories
(Core :: Graphics, defect)
Tracking
()
NEW
People
(Reporter: jrmuizel, Unassigned)
Details
Attachments
(1 file)
|
8.84 KB,
patch
|
Details | Diff | Splinter Review |
Make it possible for cairo to use floating point internally instead of fixed point. Currently the cairo choices for number representation are not that great.
Quartz on 32-bit and Direct2d both use float for there external api and quartz 64b-bit uses double. Cairo uses double and then converts that to float
| Reporter | ||
Comment 1•16 years ago
|
||
In a profile of stroking a bunch of really short lines we spend about 43.5% in _cairo_path_fixed_interpret a bunch of this time is doing number representation conversion.
| Reporter | ||
Comment 2•16 years ago
|
||
The easiest way to get this working would probably be for it to be a compile time option. Having cairo use different representations for different backends would be trickier.
| Reporter | ||
Comment 3•16 years ago
|
||
This seems to work on the simple test that I did. I've not done any other experimentation yet.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•