summaryrefslogtreecommitdiff
path: root/test/clip-operator.pdf.argb32.ref.png
AgeCommit message (Collapse)AuthorFilesLines
2011-09-15test: Move all the reference images to their own directoryChris Wilson1-0/+0
With over two thousand references images now, it is starting to make the test directory look cluttered! Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2010-12-13test: Update ref imagesAndrea Canciani1-0/+0
The recent (and not-so-recent) changes in gradient code changed the results of some tests involving gradients. radial-gradient-* tests are marked XFAIL for pdf because poppler is not sampling the color function with a sufficient frequency, but they look correct in Adobe Reader.
2010-04-30[test] Update pdf reference images for clip-operatorCarlos Garcia Campos1-0/+0
2009-08-29Update reference imagesChris Wilson1-0/+0
Refresh the test reference images to match the current output where acceptable.
2009-07-23Remove clip handling from generic surface layer.Chris Wilson1-0/+0
Handling clip as part of the surface state, as opposed to being part of the operation state, is cumbersome and a hindrance to providing true proxy surface support. For example, the clip must be copied from the surface onto the fallback image, but this was forgotten causing undue hassle in each backend. Another example is the contortion the meta surface endures to ensure the clip is correctly recorded. By contrast passing the clip along with the operation is quite simple and enables us to write generic handlers for providing surface wrappers. (And in the future, we should be able to write more esoteric wrappers, e.g. automatic 2x FSAA, trivially.) In brief, instead of the surface automatically applying the clip before calling the backend, the backend can call into a generic helper to apply clipping. For raster surfaces, clip regions are handled automatically as part of the composite interface. For vector surfaces, a clip helper is introduced to replay and callback into an intersect_clip_path() function as necessary. Whilst this is not primarily a performance related change (the change should just move the computation of the clip from the moment it is applied by the user to the moment it is required by the backend), it is important to track any potential regression: ppc: Speedups ======== image-rgba evolution-20090607-0 1026085.22 0.18% -> 672972.07 0.77%: 1.52x speedup ▌ image-rgba evolution-20090618-0 680579.98 0.12% -> 573237.66 0.16%: 1.19x speedup ▎ image-rgba swfdec-fill-rate-4xaa-0 460296.92 0.36% -> 407464.63 0.42%: 1.13x speedup ▏ image-rgba swfdec-fill-rate-2xaa-0 128431.95 0.47% -> 115051.86 0.42%: 1.12x speedup ▏ Slowdowns ========= image-rgba firefox-periodic-table-0 56837.61 0.78% -> 66055.17 3.20%: 1.09x slowdown ▏
2009-07-13[test] Track XFAIL using expected results stored as xfail.pngChris Wilson1-0/+0
Instead of tagging the sources, which is insensitive to changes, track the known failure modes by recording the current fail as an xfail.png reference. (We also introduce a new.png to track a fresh error, so that they are not lost in the noise of the old XFAILs and hopefully do not cause everyone to fret). As we have removed the XFAIL tagging we find, surprise surprise, that some tests are now working -- so review all the reference images (as also some .ref.png now should be .xfail.png). Note: I've only checked image,pdf,ps,svg. The test surfaces report some failures that probably need to addressed in source. I've not correct the changes for win32 and quartz. Nor fixed up the experimental backends.
2009-07-02[test] Update argb32 pdf reference image for clip-operatorCarlos Garcia Campos1-0/+0
2008-12-07[cairo-spans] Render clip mask surfaces with spans if we can.M Joonas Pihlaja1-0/+0
Generating surface masks for clipping can also benefit from span rendering sometimes.
2008-12-07[cairo-spans] Hook up filling paths with spans to cairo-surface-fallback.c.M Joonas Pihlaja1-0/+0
This speeds up the mask generation step in cairo_fill() for the image surface by up to 10x in especially favourable cases. image-rgba twin-800 7757.80 0.20% -> 749.41 0.29%: 10.36x speedup image-rgba spiral-diag-pixalign-nonzero-fill-512 15.16 0.44% -> 3.45 8.80%: 5.54x speedup More typical simple non-rectilinear geometries are sped up by 30-50%. This patch does not affect any stroking operations or any fill operations of pixel aligned rectilinear geometries; those are still rendered using trapezoids.
2008-10-31[test] Use '.' as the field separator in the namesChris Wilson1-0/+0
We frequently use '-' within the test name or format name and so we encounter confusion as '-' is also used as the field separator. At times this has caused a new test to break an old test because the new test would match one of the old test's target specific reference images. So switch everything over to use '.' between fields (test name, target, format, subtest, etc.).