Backed out changesets 75e7f32c3365, eec946b59360, 72a6f5f3512c, ea8ee40ed426 (bug 1412090) for apparently breaking all system-installed fonts on some Linux systems. r=backout

Bug 1416048 - Use uint32_t for DNS TTL data. r=valentin

Bug 1403438 - Add profiler-lul on mips64-linux. r=sewardj

Bug 1415300 - Update Debugger frontend (11-7). r=jdescottes Taken from upstream commit: be179268c9b89390c13bdc9c4cca6000f6f583e5 Added skip-if true to some new debugger mochitests that still look intermittent. MozReview-Commit-ID: EIcx5z9s7XF

Bug 1408403 - disable talos-g2-e10s on ccov builds. r=dustin

Don't do PaintThebes after PaintOffMainThread. (bug 1399692 part 10, r=dvander) MozReview-Commit-ID: J0IOzqIGRtz

Don't reuse a back buffer after a swap if the content or surface changed (bug 1399692 part 9, r=bas) MozReview-Commit-ID: HGAxkeyESbc

Don't copy over regions that will be painted in this frame (bug 1399692 part 8, r=bas) We do the same in FinalizeFrame, so we should do it here. MozReview-Commit-ID: JTKDj8yrtI2

Replay buffer commands on paint thread when OMTP is enabled (bug 1399692 part 7, r=bas) This commit does the work of actually dispatching the recorded buffer operations to the paint thread, and removing some main thread asserts from TextureClient. MozReview-Commit-ID: CN3RoQPz9fP

Record buffer operations to a struct for replaying on paint thread (bug 1399692 part 6, r=bas) This commit adds a CapturedBufferState which is used to record all the operations that are necessary for preparing the buffers. The commands are then instantly executed to preserve the same behavior, but in the following commit they will be dispatched to the paint thread. Note: RotatedBuffer's aren't thread safe and so a shallow copy needs to be made for sending to the paint thread. This complicates the code for AdjustTo as it can fail naturally and the buffer parameter changes are needed later in BeginPaint. So the code for AdjustTo is split up a bit to accomodate that. MozReview-Commit-ID: FwSwFay887o

Simplify copying the front buffer to the back buffer (bug 1399692 part 5, r=bas) To sync the back buffer with the front buffer, we set the back buffer rect and rotation to the front buffer's, and then copy over the pixels that different. We used to do the updating of the rect and rotation before BeginPaint, but that isn't necessary and we can move it to be with the copying of pixels. MozReview-Commit-ID: HzBKvMZkn1

Don't create back buffer for front buffer until we know what type to create. (bug 1399692 part 4, r=bas) This commit is an optimization for double buffering that delays the creation of a back buffer until we know what kind of content type it needs to be. Before this commit, we would EnsureBackBufferIfFrontBuffer before BeginPaint, then in BeginPaint we could determine that we actually needed a different kind of buffer because the content changed type, and recreate it. This was needed because BeginPaint would copy the old front buffer to the buffer created by EnsureBackBufferIfFrontBuffer, and then if anything failed or we had determined we couldn't reuse the buffer, we would create a new one and copy that "temporary" back buffer over, and use the new one. This is unnecessary because we only need read access on that "temporary" back buffer, and so we can just use the current front buffer instead. This optimization only affects the double buffered case, and the single buffered or basic cases should remain the same. Note: Because we now need the front buffer for copying into the new back buffer, we cannot Clear() it away in some error cases. Note: The code in FinalizeFrame assumes that the back and front buffer have the same size. This was implicitly enforced before, and now needs to be explicitly enforced. This commit tries to preserve the exact same behavior, although the restriction should be removed as long as the back buffer is large enough for the visible region. MozReview-Commit-ID: 2hyrrUhA4zO

Remove BufferContentType and add ValidBufferSize (bug 1399692 part 3, r=bas) BufferContentType and BufferSizeOkFor make more sense as general functions for any RotatedBuffer, and this helps out in a later patch. MozReview-Commit-ID: EAVodvl4WTu

Simplify the code for creating a new back buffer (bug 1399692 part 2, r=bas) MozReview-Commit-ID: D28JNYWD9Uc

Remove unneeded lambda capture in paint thread (bug 1399692 part 1, r=bas) MozReview-Commit-ID: 71X22PHRTRz

Bug 1341234 - part 3 - add various system library CFLAGS to BINDGEN_SYSTEM_FLAGS; r=gps This change ensures that folks who configure --with-system-FOO for various values of FOO can build Stylo, since bindgen will know where to find the flags for said FOO packages.

Bug 1341234 - part 2 - add an intermediate step for determining bindgen's CFLAGS; r=gps Add an intermediate step in old-configure.in for setting up BINDGEN_CFLAGS (renamed to BINDGEN_SYSTEM_FLAGS), so we can add whatever flags we like (e.g. for system libaries with their includes in non-standard places) at a later point.

Bug 1341234 - part 1 - add AC_SUBST_TOML_LIST macro; r=gps Stylo's bindgen is configured partially through a .toml.in file that substitutes the value of a configure variable (BINDGEN_CFLAGS) into a TOML list. We can debate whether this is a good thing to do some other time; the reality is that the current moz.configure code that provides the set_config for BINDGEN_CFLAGS needs to perform all the quoting itself. We want, however, to define the substituted variable in old-configure.in land (some of the values that will go into BINDGEN_CFLAGS are only defined in old-configure.in, and are not trivially ported to moz.configure), which means that we need to have quoting logic in m4/Python when we generate config.status. This patch adds an appropriate macro for doing so.

Bug 1341234 - part 0 - fix typo in AC_SUBST_SET checking; r=gps The various AC_SUBST macros generate AC_SUBST_*FOO macros for holding the values to substitute. The macros also cross-check the AC_SUBST_* macros generated by other variants to make sure that you don't try to do something like AC_SUBST(FOO) and AC_SUBST_SET(FOO). However, the check in AC_SUBST_SET for AC_SUBST_LIST duplicate is missing an underscore: the AC_SUBST_LIST macro generates another macro starting with AC_SUBST_LIST_, but the AC_SUBST_SET macro checks for the prefix AC_SUBST_LIST, which is missing the trailing underscore. As we're going to be adding yet another AC_SUBST_* macro variant, and therefore adding more checks to all existing macros, let's clean this up before we start.

Bug 1413937 - add sha384 and sha512 to pycert and pykey, r=keeler MozReview-Commit-ID: ArjNHLC1MFC Differential Revision: https://phabricator.services.mozilla.com/D185