Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upSync changes from mozilla-central gfx/wr #3872
Merged
+2,545
−590
Conversation
…ity_binding. r=gw The return value is not used at all. Differential Revision: https://phabricator.services.mozilla.com/D63600 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/921116ca67a59fb323b74d1a610249c2448101d7
Differential Revision: https://phabricator.services.mozilla.com/D63601 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/737f4bc3afd3e823fd3f0e253388789a8c0d0299
Differential Revision: https://phabricator.services.mozilla.com/D63603 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/6b3af91a7ce6e5aee774cdde1c0dc5e2da7bebae
…mations on the compositor. r=gw,boris Differential Revision: https://phabricator.services.mozilla.com/D63604 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/087518046b0c65aebc0c976bf2f736acf7cd4a89
Backed out changeset 28a2fba71977 (bug 1510030) Backed out changeset 1700b3a416cd (bug 1510030) Backed out changeset 087518046b0c (bug 1510030) Backed out changeset 6b3af91a7ce6 (bug 1510030) Backed out changeset 737f4bc3afd3 (bug 1510030) Backed out changeset 921116ca67a5 (bug 1510030) [ghsync] From https://hg.mozilla.org/mozilla-central/rev/7fc17499b72099c0fa5d27f76c619229c01f2516
…ity_binding. r=gw The return value is not used at all. Differential Revision: https://phabricator.services.mozilla.com/D63600 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/b3dfa17c6305c657f8c3b3c95121c19f005d451c
Differential Revision: https://phabricator.services.mozilla.com/D63601 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/781cd96dd9a2d21922395d548d05e4f7ae5c155b
Differential Revision: https://phabricator.services.mozilla.com/D63603 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/b37ce2b87ac7b02a82a9caf6c45f7a4dea6d6017
…mations on the compositor. r=gw,boris Differential Revision: https://phabricator.services.mozilla.com/D63604 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/a2be11cbe3f22a0b4f121df97045f560dca8ccb4
…html failures CLOSED TREE Backed out changeset a14a131ca731 (bug 1510030) Backed out changeset a75359516fec (bug 1510030) Backed out changeset a2be11cbe3f2 (bug 1510030) Backed out changeset b37ce2b87ac7 (bug 1510030) Backed out changeset 781cd96dd9a2 (bug 1510030) Backed out changeset b3dfa17c6305 (bug 1510030) [ghsync] From https://hg.mozilla.org/mozilla-central/rev/7d06c5f0f339c0016c764d49ebe6962b177a1e15
|
@bors-servo r=auto |
|
|
bors-servo
added a commit
that referenced
this pull request
Feb 27, 2020
Sync changes from mozilla-central gfx/wr
|
|
…ity_binding. r=gw The return value is not used at all. Differential Revision: https://phabricator.services.mozilla.com/D63600 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/fa80818e1861f83af3ee2d16de44aca23dd59294
Differential Revision: https://phabricator.services.mozilla.com/D63601 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/70a094437dfbacf8a110d015b32bdaa6936531c2
Differential Revision: https://phabricator.services.mozilla.com/D63603 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/42d17390bcca6e518624bddb755433277dd64ba4
…mations on the compositor. r=gw,boris Differential Revision: https://phabricator.services.mozilla.com/D63604 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/9092c93a4ac6621e8fb255ae5b386046a0524c0a
|
@bors-servo r=auto |
|
|
|
bors-servo
added a commit
that referenced
this pull request
Feb 27, 2020
Sync changes from mozilla-central gfx/wr
|
|
…nts in webrender. r=lsalzman Depends on D63893 Differential Revision: https://phabricator.services.mozilla.com/D64746 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/793e9dfa4b9fa40137cdf2a5d34c126d6cc9840d
…rop shadows in WebRender r=gfx-reviewers,kvark Differential Revision: https://phabricator.services.mozilla.com/D63441 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/a9d8b62a399349559ceff12111f5d7fd3fab4acc
…AX_BLUR after scale factors are applied r=gfx-reviewers,nical This was causing one of the large drop-shadow wrench reftests to timeout. This is only a partial fix, as we should be checking the scale factors earlier on when sanitizing the filter input. This will ensure we match what the non-WR backend is doing and will prevent overinflation. Differential Revision: https://phabricator.services.mozilla.com/D64197 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/b7ab4c947688fab1ee8de2ef13a6033e2307d590
|
@bors-servo r=auto |
|
…eyor CI. r=Bert Differential Revision: https://phabricator.services.mozilla.com/D65164 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/438e07547213297357465701a32a7419d6ead18f
Rather than treating webrender::intern::UpdateList as a sequence of operations, each of which might be an insertion or a removal, and using a side table to supply extra data for insertions, it's simpler to segregate insertions and removals into two separate vectors. This avoids the need for an enum whose discriminant needs to be checked within the loop, and allows a few loops that are only looking for one kind of operation to skip over the others entirely. Ultimately, there should be no change in the order in which operations occur. In practice, the old UpdateList always held a contiguous run of insertions, followed by a run of removals (removals are consumed by apply_updates directly after being generated by end_frame_and_get_pending_updates). Differential Revision: https://phabricator.services.mozilla.com/D64444 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/06e238addde26dee65ee29f3cb676d7d47ff4e6e
|
@bors-servo r=auto |
|
|
Ensure that the image keys and image generations for external compositor surfaces are included in the composite descriptor, which is used to determine if a composite is required or can be skipped. Differential Revision: https://phabricator.services.mozilla.com/D65216 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/5f2a8eb4989755c3cf987738ea04034ac5bea896
|
@bors-servo r=auto |
|
|
|
@bors-servo retry |
|
@jdm does bors need a kick? |
Add support for a `fuzzy-range` keyword in reftest.list. It is similar to `fuzzy` but it allows multiple pairs of `max_difference, num_differences` numbers that introduce multiple buckets of allowed differences. For example, `fuzzy-range(5,100,20,10)` allows at most 100 pixels with a difference of at most 5, _plus_ an extra 10 pixels at most that have a difference more than 5 but less than or equal to 20. The total number of differing pixels allowed is thus 110, but only if 100 of those differ by <= 5 and the remaining 10 by <= 20. 110 pixels with a difference <= 5 will still fail. This is intentional to encourage tighter bounds in tests where many pixels are slightly off and a few outliers are off by a lot. The number of parameters is arbitrary; longer lists can get confusing so this change also introduces optional support for writing `<=` in front of the max difference and `*` in front of the max pixel count, eg. `fuzzy-range(<=5,*100,<=20,*10)` (no spaces). Any pixels that exceed the highest maximum will fail the test, similar to `fuzzy`. Steps tested: 1. the same tests fail in exactly the same way before and after; 2. reordered the `fuzzy` statements for raster_root_A/B/C to no longer be sorted by max difference, and verified that the tests pass/fail the same way; (then sort them again which is easier to understand); 3. tests using the new feature still fail when the ref no longer matches (deliberately broke the _ref version and verified test failed); Differential Revision: https://phabricator.services.mozilla.com/D65247 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/8c07488c9a3f0a76e01ce34e060d071a2310612d
|
@bors-servo r=auto |
|
|
…r. r=gw Differential Revision: https://phabricator.services.mozilla.com/D65391 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/010e798483903efee1caac88c01ba2b172d13c09
|
@bors-servo r=auto |
|
|
bors-servo
added a commit
that referenced
this pull request
Mar 5, 2020
Sync changes from mozilla-central gfx/wr
|
|
|
Another fuzz difference in AppVeyor, put patch on https://phabricator.services.mozilla.com/D65513 |
…or. r=Bert Differential Revision: https://phabricator.services.mozilla.com/D65513 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/3c67e9f15e9361e595477f16e13e018b9aab35c0
…. r=Bert,sotaro This patch refactors how external surfaces are stored in the CompositeState structure. This is primarily to simplify integration with native compositor mode, but also simplifies the Draw compositor path. Previously, the ResolvedExternalSurface struct contained information that was used to rasterize the external surface (YUV planes etc) and also the information to composite it (device rect, clip rect, z_id). Now, ResolvedExternalSurface contains just the information required to rasterize the external surface, while the compositing information is handled by adding the external surface as a regular tile. This makes it possible to unify how external surfaces are drawn, via the common draw_tile_list method. Differential Revision: https://phabricator.services.mozilla.com/D65269 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/4bbb79cbf9cc9efc7d599d1fe8d68bf620601fc9
…taro This patch adds support for external compositor surfaces when using native compositor mode. Differential Revision: https://phabricator.services.mozilla.com/D65436 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/c3a689bf10e1dd2b1dc04fe0494584561bd8421b
…ender_task.rs:37 r=gw Adding a repro-case reftest that asks for a 19996x5000 RenderTask (at -p1), then fix it in analogy with the clamping to reasonable values that happens for `NormalBorder`. Differential Revision: https://phabricator.services.mozilla.com/D65660 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/14caf2826f00fc609f7fe55d8df14e7e08fd1ced
|
@bors-servo r=auto |
|
|
|
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
moz-gfx commentedFeb 27, 2020
No description provided.