e1f22d19eb6933f2ffc3dc9b78b0cf66d8648474: Bug 1444141 - part 4 - make the JS engine depend on Rust; r=chmanchester,glandium,jorendorff
Nathan Froyd <froydnj@mozilla.com> - Thu, 02 Aug 2018 11:00:21 -0500 - rev 825942
Push 118215 by bmo:mtigley@mozilla.com at Thu, 02 Aug 2018 18:26:57 +0000
Bug 1444141 - part 4 - make the JS engine depend on Rust; r=chmanchester,glandium,jorendorff The Rust dependency in Firefox has been limited to Firefox builds by virtue of having the Rust check in a Firefox-specific location, toolkit/moz.configure. For JS to start depending on Rust, we need to move that check to a location where a standalone JS engine build will pick up the Rust check.
6c0285701a15fd779cb7964bb434f7841ecfd1d7: Bug 1444141 - part 3 - fix exports of PATH in sm-tooltool-config.sh; r=sfink
Nathan Froyd <froydnj@mozilla.com> - Thu, 02 Aug 2018 12:00:21 -0400 - rev 825941
Push 118215 by bmo:mtigley@mozilla.com at Thu, 02 Aug 2018 18:26:57 +0000
Bug 1444141 - part 3 - fix exports of PATH in sm-tooltool-config.sh; r=sfink TOOLTOOL_CHECKOUT is typically `.`, which doesn't work so great for adding things to $PATH. We need to turn everything we're adding to $PATH into absolute paths, so $PATH actually works properly.
74d0193f2bd34cc15a17d02db9e675f5c83d657b: Bug 1444141 - part 2 - make some spidermonkey tasks depend on rust; r=sfink
Nathan Froyd <froydnj@mozilla.com> - Thu, 02 Aug 2018 11:00:21 -0500 - rev 825940
Push 118215 by bmo:mtigley@mozilla.com at Thu, 02 Aug 2018 18:26:57 +0000
Bug 1444141 - part 2 - make some spidermonkey tasks depend on rust; r=sfink Spidermonkey tasks have not had to depend on Rust before, but since we're about to add a dependency on Rust to the JS engine, we need Rust binaries.
bb730dc5b37521c0c80342ba7c83278b2dc313d2: Bug 1444141 - part 1 - export RUSTC and CARGO variables for the hazard analysis build; r=sfink
Nathan Froyd <froydnj@mozilla.com> - Thu, 02 Aug 2018 11:00:21 -0500 - rev 825939
Push 118215 by bmo:mtigley@mozilla.com at Thu, 02 Aug 2018 18:26:57 +0000
Bug 1444141 - part 1 - export RUSTC and CARGO variables for the hazard analysis build; r=sfink configure needs these environment variables to find rustc and cargo.
f5b648ddfe64f952541cf00f948824c7590b73a2: Bug 1465491 Part 2 - Helper functions for web replay mochitests, r=jryans.
Brian Hackett <bhackett1024@gmail.com> - Thu, 02 Aug 2018 15:37:20 +0000 - rev 825938
Push 118215 by bmo:mtigley@mozilla.com at Thu, 02 Aug 2018 18:26:57 +0000
Bug 1465491 Part 2 - Helper functions for web replay mochitests, r=jryans.
32e585dc283643b1db173243cbccdfe32c5c2042: Bug 1479812 - Update Debugger Frontend v77. r=dwalsh
Jason Laster <jason.laster.11@gmail.com> - Wed, 01 Aug 2018 15:42:00 -0400 - rev 825937
Push 118215 by bmo:mtigley@mozilla.com at Thu, 02 Aug 2018 18:26:57 +0000
Bug 1479812 - Update Debugger Frontend v77. r=dwalsh
0e438cdb3c51543654fc866b9d85673f5e0f9ec5: Bug 1479672 - Remove --enable-stdcxx-compat option from JS shell being analyzed for hazards, r=jonco
Steve Fink <sfink@mozilla.com> - Thu, 05 Jul 2018 15:25:12 -0700 - rev 825936
Push 118215 by bmo:mtigley@mozilla.com at Thu, 02 Aug 2018 18:26:57 +0000
Bug 1479672 - Remove --enable-stdcxx-compat option from JS shell being analyzed for hazards, r=jonco
c044ba304147da2262804a4285637afc94330192: Bug 1475446 - Use in-tree zlib for msan, r=jonco
Steve Fink <sfink@mozilla.com> - Wed, 11 Jul 2018 17:35:10 -0700 - rev 825935
Push 118215 by bmo:mtigley@mozilla.com at Thu, 02 Aug 2018 18:26:57 +0000
Bug 1475446 - Use in-tree zlib for msan, r=jonco
02a2ba8de75cac1d36c7c2be7421827bdc9f724f: Bug 1469965 - Display trigger threshold exceeded in MOZ_GCTIMER output, r=pbone
Steve Fink <sfink@mozilla.com> - Wed, 16 May 2018 16:15:12 -0700 - rev 825934
Push 118215 by bmo:mtigley@mozilla.com at Thu, 02 Aug 2018 18:26:57 +0000
Bug 1469965 - Display trigger threshold exceeded in MOZ_GCTIMER output, r=pbone
93516631d63527d285b518f7d5e3b8aa800b627a: Bug 1479777 - Reduce clang-cl warnings from mozglue/misc/interceptor/. r=aklotz
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Tue, 31 Jul 2018 22:03:43 +0900 - rev 825933
Push 118215 by bmo:mtigley@mozilla.com at Thu, 02 Aug 2018 18:26:57 +0000
Bug 1479777 - Reduce clang-cl warnings from mozglue/misc/interceptor/. r=aklotz
13dcbc780bd06d26b4a437578706995632703f4e: Bug 1473313 - Part 5: Add in-tree documentation page for Android code coverage. r=nalexander draft
Tudor-Gabriel Vîjială <tvijiala@mozilla.com> - Tue, 31 Jul 2018 12:02:08 +0100 - rev 825932
Push 118214 by bmo:tvijiala@mozilla.com at Thu, 02 Aug 2018 18:25:01 +0000
Bug 1473313 - Part 5: Add in-tree documentation page for Android code coverage. r=nalexander MozReview-Commit-ID: 20meKbpduha
c35817ef16bcdc166faa6741c7b3d46bd44b450e: Bug 1476793 - Teach HelperThread how to push/pop profiler label frames, and use this capability to push an IDLE frame when the thread is idle. r?njn, r?sfink draft
Markus Stange <mstange@themasta.com> - Thu, 02 Aug 2018 13:49:48 -0400 - rev 825931
Push 118213 by bmo:mstange@themasta.com at Thu, 02 Aug 2018 18:21:17 +0000
Bug 1476793 - Teach HelperThread how to push/pop profiler label frames, and use this capability to push an IDLE frame when the thread is idle. r?njn, r?sfink MozReview-Commit-ID: 6HIWrA27X87
f7740ac5fc895b681942bc4f4446bb00129b17f8: Annotate idle stacks in the chromium event loop on Windows. draft
Markus Stange <mstange@themasta.com> - Sat, 09 Jun 2018 15:50:10 -0400 - rev 825930
Push 118213 by bmo:mstange@themasta.com at Thu, 02 Aug 2018 18:21:17 +0000
Annotate idle stacks in the chromium event loop on Windows.
42115d88eece3f162213f87138d2f98bb52c42ab: Annotate idle stacks in the StorageDB thread. draft
Markus Stange <mstange@themasta.com> - Sat, 09 Jun 2018 15:45:21 -0400 - rev 825929
Push 118213 by bmo:mstange@themasta.com at Thu, 02 Aug 2018 18:21:17 +0000
Annotate idle stacks in the StorageDB thread.
c14c4ce163d458275e1392fab674e8b70fca43f9: Make layout.display-list.dump also dump the frame tree on every paint. draft
Markus Stange <mstange@themasta.com> - Tue, 03 Nov 2015 12:34:50 +0100 - rev 825928
Push 118213 by bmo:mstange@themasta.com at Thu, 02 Aug 2018 18:21:17 +0000
Make layout.display-list.dump also dump the frame tree on every paint. MozReview-Commit-ID: I1OBPtYMfNb
07bd989c674d7c54b1b2973826429e4d2a2a856e: Bug 1465924 - Add a new optional property called "processName" to profile.meta which contains "Main Process" in the parent process and a content process name like "WebExtensions" for special content processes, see ContentChild::RecvRemoteType. r?gregtatum draft
Markus Stange <mstange@themasta.com> - Thu, 31 May 2018 14:51:37 -0400 - rev 825927
Push 118213 by bmo:mstange@themasta.com at Thu, 02 Aug 2018 18:21:17 +0000
Bug 1465924 - Add a new optional property called "processName" to profile.meta which contains "Main Process" in the parent process and a content process name like "WebExtensions" for special content processes, see ContentChild::RecvRemoteType. r?gregtatum This field is in addition to the two existing process type fields we already have: - profile.meta.processType contains the integer value of the GeckoProcessType enum for the process. - profile.threads[i].processType contains the string for that GeckoProcessType. MozReview-Commit-ID: 3Pg6M1D6uDf
0510dcafc5087e6c3279835c3ab03e140b15b3a8: Bug 1476775 - Proof of concept: Discard samples that are older than 20 seconds. draft
Markus Stange <mstange@themasta.com> - Wed, 23 May 2018 23:52:21 -0400 - rev 825926
Push 118213 by bmo:mstange@themasta.com at Thu, 02 Aug 2018 18:21:17 +0000
Bug 1476775 - Proof of concept: Discard samples that are older than 20 seconds. MozReview-Commit-ID: 693hds9Edss
12e6e08f601e9adaf9b9710cc6aed606d855f1e1: Bug 1476757 - WIP: Grow and shrink the profiler buffer dynamically so as to not waste memory when a large buffer size limit is picked. draft
Markus Stange <mstange@themasta.com> - Tue, 22 May 2018 17:30:08 -0400 - rev 825925
Push 118213 by bmo:mstange@themasta.com at Thu, 02 Aug 2018 18:21:17 +0000
Bug 1476757 - WIP: Grow and shrink the profiler buffer dynamically so as to not waste memory when a large buffer size limit is picked. I haven't run tests on this yet, and I haven't checked what the implications of changing the meaning of "entry size" are for all consumers of this piece of data. In the past, the buffer "entry size" (which is really more of a count than a size) referred to the actual current capacity of the buffer. Now it refers to the maximum capacity. I think we need to audit especially the callers of profiler_get_buffer_info(): - The gtests - and the old performance devtool, which uses nsIProfiler.getBufferInfo to draw a progress bar during capturing, and makes chunking decisions based on it. MozReview-Commit-ID: 4c26L5MhN2e
e0904257631f125ab555c9b2d8d3be94b75cb74d: Bug 1476757 - Add methods to change the capacity of the ProfileBuffer. draft
Markus Stange <mstange@themasta.com> - Mon, 21 May 2018 11:11:12 -0400 - rev 825924
Push 118213 by bmo:mstange@themasta.com at Thu, 02 Aug 2018 18:21:17 +0000
Bug 1476757 - Add methods to change the capacity of the ProfileBuffer. MozReview-Commit-ID: 1sHsJz0oBvU
98a9070b483ea418a746e0f56baafbdee11a5ad5: Bug 1475543 - Build rust as 64-bit binary for mingw targets r?froydnj draft
Jacek Caban <jacek@codeweavers.com> - Mon, 30 Jul 2018 11:36:04 -0500 - rev 825923
Push 118212 by bmo:tom@mozilla.com at Thu, 02 Aug 2018 18:17:47 +0000
Bug 1475543 - Build rust as 64-bit binary for mingw targets r?froydnj MozReview-Commit-ID: HOIclifAZXg
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 tip