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 #3870
Merged
+1,144
−318
Conversation
…t r=kvark Differential Revision: https://phabricator.services.mozilla.com/D63227 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/3a8d5795c985cb609bf26c0900e4a9ded3514943
…isplay_list.rs. CLOSED TREE [ghsync] From https://hg.mozilla.org/mozilla-central/rev/6f4560630238502bc8ad26351b65fbb7189a9e96
…t r=kvark Differential Revision: https://phabricator.services.mozilla.com/D63227 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/cee2ebb35aa78184cfdd1064eb965acc22b0ee4a
|
@bors-servo r=auto |
|
|
bors-servo
added a commit
that referenced
this pull request
Feb 21, 2020
Sync changes from mozilla-central gfx/wr
|
|
If a memory pressure event arrives _after_ a new scene has been published that writes persistent targets (i.e. cached render tasks to the texture cache, or picture cache tiles) but _before_ the next update/render loop, those targets will not be updated due to the active_documents list being cleared at the end of this message. To work around that, if any of the existing documents have not rendered yet, and have picture/texture cache targets, force a render so that those targets are updated. Differential Revision: https://phabricator.services.mozilla.com/D63593 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/c43cfbdad21614b771c8760afcc59ef63960e438
|
@bors-servo r=auto |
|
|
|
…ext to avoid quantization effects. r=lsalzman Currently we quantize the snapped reference frame relative offset used in the shader in order to stuff it in our extra integer parameter fields in the prim header. Since we don't use the prim rect size for anything in the text shader, this patch just puts it there instead, and avoids quantizing that. Differential Revision: https://phabricator.services.mozilla.com/D63639 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/26d8dfb033cec949f38582fe6e8fb8200b84b44b
It's unclear what this was accomplishing, but it prevents us from correctly processing the pixels on the edge of the mask, causing masked content to peek through. No tests seem to rely on this discarding behaviour. Also added a reftest that's fairly fuzzy but should suffice as a canary for a regression here. Differential Revision: https://phabricator.services.mozilla.com/D63344 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/ed0609ec00baad84416ee89012c7138907216989
…stages. CLOSED TREE [ghsync] From https://hg.mozilla.org/mozilla-central/rev/4eb218fb5806b04c040ff4bfdd7eb2fce4b8d6cb
|
@bors-servo r=auto |
|
|
…transform. r=lsalzman This patch folds the raster scale and device pixel scale effects into the font transform, instead of the font size itself. This helps minimize the quantization effect given the font size is stored as an Au (resolution of 1/60) instead of an f32, and the shader does not replicate that effect. Differential Revision: https://phabricator.services.mozilla.com/D63641 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/3b8e7a5e093d7ba4717d3914a07ac46e59cdf8b9
…ustages. CLOSED TREE [ghsync] From https://hg.mozilla.org/mozilla-central/rev/88029a1e5e5ae1aab7ede64d4cf95d78dfd53911
…=botond,jrmuizel Differential Revision: https://phabricator.services.mozilla.com/D60046 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/8665af6e62a69fa2a7fb5de84294f8947986d25d
|
@bors-servo r=auto |
|
|
… r=nical If only a single segment is produced, there is no benefit to writing a segment instance array. Instead, just use the main primitive rect written into the GPU cache. Differential Revision: https://phabricator.services.mozilla.com/D63812 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/20cf567a6dcff0ac0d4ebfa4d030cabdd99a96e2
Move the UV writing function into the shared yuv.glsl include so that the YUV compositing shader will be able to access it. Differential Revision: https://phabricator.services.mozilla.com/D63815 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/b22c07ea7c728cc962094c94d18aeed414c4936a
… CLOSED TREE [ghsync] From https://hg.mozilla.org/mozilla-central/rev/8c5f9b08938ed193c756b6bc9884a353b796a55f
|
@bors-servo r=auto |
|
|
…transform. r=lsalzman This patch folds the raster scale and device pixel scale effects into the font transform, instead of the font size itself. This helps minimize the quantization effect given the font size is stored as an Au (resolution of 1/60) instead of an f32, and the shader does not replicate that effect. Differential Revision: https://phabricator.services.mozilla.com/D63641 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/dd93a477ee7892007db8810030e41081529ca0dc
Original patch by Josh Mattews in #3854 Also run mach vendor rust. Differential Revision: https://phabricator.services.mozilla.com/D63468 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/792590f6d2e5007fd7991c5b78b22726dec59d3d
…muizel Previously we only saved shaders to disk on the tenth frame, meaning shaders compiled afterwards would not be cached and would need to be recompiled in future runs of the application. This change makes it so that we cache shaders to disk regardless of which frame they are compiled in. We continue to treat only the shaders used within the first ten frames as the "startup shaders", meaning only those ones will be loaded on next startup. Caching as many other shaders as possible is still beneficial, however, as they are loaded on-demand. Differential Revision: https://phabricator.services.mozilla.com/D62748 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/de1a62be4e5769c30ec3925c0660da31069c9964
and others
added 6 commits
Feb 25, 2020
…tKey. r=gw Differential Revision: https://phabricator.services.mozilla.com/D63965 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/681bd0c06055bf9d86a5462c78b830ca7520c742
…onal checks r=jrmuizel Differential Revision: https://phabricator.services.mozilla.com/D63275 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/d17dbf82cdd08e6911b204f8196bbe1948932cb5
…reateWebRenderCommands() r=jrmuizel Differential Revision: https://phabricator.services.mozilla.com/D63276 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/3d44ebc7aed0821fa4bd8b9be0a9d47fd216aa29
… failures CLOSED TREE Backed out changeset 3d44ebc7aed0 (bug 1616422) Backed out changeset d17dbf82cdd0 (bug 1616422) [ghsync] From https://hg.mozilla.org/mozilla-central/rev/7ab2d5774c5e936edb667d4c0fedca124472dd19
…onal checks r=jrmuizel Differential Revision: https://phabricator.services.mozilla.com/D63275 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/a1d378c9227f4a48dfa7b76f16e51b0eee23636c
…reateWebRenderCommands() r=jrmuizel Differential Revision: https://phabricator.services.mozilla.com/D63276 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/2ae6d9dfdbc517cc1b0cf7c4a7f9e138f6e75707
|
@bors-servo r=auto |
|
|
…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/889cee140af8177fbf144bffdf3c68f587f1aa56
…n a CLOSED TREE Backed out changeset 49e61b566da1 (bug 1596513) Backed out changeset 889cee140af8 (bug 1596513) [ghsync] From https://hg.mozilla.org/mozilla-central/rev/e9a85eb47d024d9defa5e0a0eaf17c6403eddf98
|
@bors-servo r=auto |
|
|
…r mode. r=Bert This patch adds support for YUV images to be promoted to compositor surfaces when using the simple (draw) compositor mode. A follow up to this will extend support to native compositor implementations. We rely on only promoting compositor surfaces that are opaque primitives. With this assumption, the tile(s) that intersect the compositor surface get a 'cutout' in the location where the compositor surface exists, allowing that tile to be drawn as an overlay after the compositor surface. Tiles are only drawn in overlay mode if there is content that exists on top of the compositor surface. Otherwise, we can draw the tiles in the normal fast path before the compositor surface is drawn. The patch also introduces a new subpixel AA mode, which allows subpixel rendering to be enabled conditionally as long as the text run does not intersect some number of excluded rectangle regions. In this way, subpixel text remains on most of the page, but is disabled for elements that are drawn into transparent regions of the tile where the compositor surface exists. This allows video playback to be composited directly into the framebuffer, without invalidation of content tiles, which can save a significant amount of battery power and improve performance. Differential Revision: https://phabricator.services.mozilla.com/D63816 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/238379209ef45c45fa1fd78960d16b10a266097e
…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/edc3c212be1fefa3b05200d1d7665be28e40167e
Differential Revision: https://phabricator.services.mozilla.com/D63601 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/c3e6c17ba7b0cae28b49a99836a5814264fd4825
Differential Revision: https://phabricator.services.mozilla.com/D63603 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/cd729f8b02207a2e44396e7886fbeb7d97543c75
…mations on the compositor. r=gw,boris Differential Revision: https://phabricator.services.mozilla.com/D63604 [ghsync] From https://hg.mozilla.org/mozilla-central/rev/ec9c6b79ea42a6624090806f06ce1079b1a7248e
…SED TREE Backed out changeset 1bf2a082ca62 (bug 1510030) Backed out changeset 8b0fd12a063b (bug 1510030) Backed out changeset ec9c6b79ea42 (bug 1510030) Backed out changeset cd729f8b0220 (bug 1510030) Backed out changeset c3e6c17ba7b0 (bug 1510030) Backed out changeset edc3c212be1f (bug 1510030) [ghsync] From https://hg.mozilla.org/mozilla-central/rev/7a5cb26a2d518e9cfaf512ba9a06239b573d7f0e
|
@bors-servo r=auto |
|
|
|
|
This was referenced Feb 27, 2020
Closed
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 21, 2020
No description provided.