Bug 35547 - Intermediate regions in libpixman aren't clipped to image
Summary: Intermediate regions in libpixman aren't clipped to image
Status: RESOLVED MOVED
Alias: None
Product: pixman
Classification: Unclassified
Component: pixman (show other bugs)
Version: git master
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Søren Sandmann Pedersen
QA Contact: Søren Sandmann Pedersen
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-22 08:26 UTC by Søren Sandmann Pedersen
Modified: 2018-06-05 15:27 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Søren Sandmann Pedersen 2011-03-22 08:26:22 UTC
This bug has come full circle. The server's software implementation has moved to pixman, so now this is a pixman bug. I'm leaving 2462 open since EXA/UXA have duplicated the code that contained the bug.


+++ This bug was initially created as a clone of Bug #2462 +++

In libpixman/ictrap.c:pixman_composite_trapezoids(), the bounding
box of the intermediate surface needs to be intersected with the
bounding box of the image (bailing immediately on empty intersection).

This should help a *lot* when zoomed in on a larger image.
Comment 1 Søren Sandmann Pedersen 2011-03-22 08:37:10 UTC
The bug here is in pixman_composite_trapezoids() the intermediate alpha image should only be the size of the clip region. This would prevent the rasterization of invisible trapezoids.
Comment 2 Siarhei Siamashka 2014-09-21 22:12:23 UTC
The importance seems to be set to 'high' for this bug. Is it just a performance problem? Do we have a simple testcase for it?
Comment 3 GitLab Migration User 2018-06-05 15:27:21 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pixman/pixman/issues/12.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.