358949058ff872d8ce1b07bc013486c9ffd92ce2: Bug 1205053 - use registry typedURLs to import rudimentary history from MS Edge, r=dolske
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Tue, 15 Sep 2015 22:18:41 +0100 - rev 295372
Push 5662 by nalexander@mozilla.com at Tue, 22 Sep 2015 17:20:59 +0000
Bug 1205053 - use registry typedURLs to import rudimentary history from MS Edge, r=dolske
2d5d44ba3a86cbe3ddd5fd52255c3c400019c211: Bug 1200892 - fix devedition styling of window in fullscreen on vista/win7, r=bgrins
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Thu, 17 Sep 2015 15:47:05 +0100 - rev 295371
Push 5662 by nalexander@mozilla.com at Tue, 22 Sep 2015 17:20:59 +0000
Bug 1200892 - fix devedition styling of window in fullscreen on vista/win7, r=bgrins
b2896463ae0a35336e5a805ddbaae9c3995c5e26: Bug 1204356 - fix back button state on devedition when mouse is not over open back button, r=bgrins
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Thu, 17 Sep 2015 16:06:18 +0100 - rev 295370
Push 5662 by nalexander@mozilla.com at Tue, 22 Sep 2015 17:20:59 +0000
Bug 1204356 - fix back button state on devedition when mouse is not over open back button, r=bgrins
30d61283668592adfaec7a00aeeabc9d32a688c2: Bug 1192924: Check for updated system add-ons and download and install them. r=rhelmer
Dave Townsend <dtownsend@oxymoronical.com> - Thu, 10 Sep 2015 10:57:39 -0700 - rev 295369
Push 5662 by nalexander@mozilla.com at Tue, 22 Sep 2015 17:20:59 +0000
Bug 1192924: Check for updated system add-ons and download and install them. r=rhelmer This performs the update check for system add-ons. It runs as part of the daily add-on update checks similar to hotfix checks. Currently no URL is set so builds won't actually start checking yet. I've taken a few shortcuts here by only staging updates and needing a restart to install as well as always downloading updates rather than using existing local copies. At least the latter probably needs fixing before turning this on but it makes more sense to iterate on those in tree.
a6860f880e01572924f05421adf26bee06a72cb4: Bug 1192924: Split out add-on update.xml parsing code from GMP modules. r=spohl
Dave Townsend <dtownsend@oxymoronical.com> - Tue, 08 Sep 2015 15:00:28 -0700 - rev 295368
Push 5662 by nalexander@mozilla.com at Tue, 22 Sep 2015 17:20:59 +0000
Bug 1192924: Split out add-on update.xml parsing code from GMP modules. r=spohl The system add-on update checks will use the same update.xml format as GMP so this splits out the code for parsing and downloading files into a standalone module that both can reuse.
10e1fa2cc23a348e0266d28a76bf932fd2efdf2f: Bug 1192924: Expose the update URL formatting code a new UpdateUtils module. r=rstrong
Dave Townsend <dtownsend@oxymoronical.com> - Mon, 14 Sep 2015 11:04:19 -0700 - rev 295367
Push 5662 by nalexander@mozilla.com at Tue, 22 Sep 2015 17:20:59 +0000
Bug 1192924: Expose the update URL formatting code a new UpdateUtils module. r=rstrong The GMP manager uses a copy of the update service's url formatting code and has since fallen out of sync. We'll also want to use the same formatting code for the system add-on update checks so this just exposes it in a shared API. I've moved the contents of UpdateChannel.jsm to UpdateUtils.jsm and exposed formatUpdateURL there as well as a few properties that the update service still needs access to. UpdateUtils.UpdateChannel is intended to be a lazy getter but isn't for now since tests expect to be able to change the update channel at runtime.
71b9f9b7a1116bce4f3911949058f2d8291c5f7b: Bug 1193215 - Support for passing test directories through mach try. draft
James Graham <james@hoppipolla.co.uk> - Tue, 22 Sep 2015 17:55:29 +0100 - rev 295366
Push 5661 by james@hoppipolla.co.uk at Tue, 22 Sep 2015 16:56:26 +0000
Bug 1193215 - Support for passing test directories through mach try. This adds support for web-platform-tests to mach try. It changes the implementation so that instead of passing paths to manifests, the user passes arbitary paths in the source tree, and tests under that path are run, with test discovery mainly left to the harness.
724490d3f4901527a72e1c21a16b5a45b048ec9e: bug 1170987 - Fix gfx/2d to build on iOS. r?jrmuizel draft
Ted Mielczarek <ted@mielczarek.org> - Fri, 12 Jun 2015 08:48:42 -0400 - rev 295365
Push 5660 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:28:22 +0000
bug 1170987 - Fix gfx/2d to build on iOS. r?jrmuizel
38bad6c8839550f30d3e931348db1182821cc6b4: bug 1174415 - Make gfx build for iOS. r?jrmuizel draft
Ted Mielczarek <ted.mielczarek@gmail.com> - Tue, 22 Sep 2015 12:21:40 -0400 - rev 295364
Push 5659 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:25:32 +0000
bug 1174415 - Make gfx build for iOS. r?jrmuizel
07b68a55926b2f03aa02787db43fa7d29d36d2a5: bug 1174415 - Make gfx build for iOS. r?jrmuizel draft
Ted Mielczarek <ted.mielczarek@gmail.com> - Tue, 18 Aug 2015 14:36:45 -0400 - rev 295363
Push 5658 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:19:55 +0000
bug 1174415 - Make gfx build for iOS. r?jrmuizel
90a81eca970022bbb5a3127db7bdc47ec170c3fd: Bug 1170986 - Use Core Text APIs instead of Cocoa font manager wherever possible in gfxMacPlatformFontList. draft
Jonathan Kew <jkew@mozilla.com> - Tue, 22 Sep 2015 09:34:10 -0400 - rev 295362
Push 5658 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:19:55 +0000
Bug 1170986 - Use Core Text APIs instead of Cocoa font manager wherever possible in gfxMacPlatformFontList.
1234556fc3f5eb7e1706e684a42570eb98f6b23e: bug 1174703 - Add GLContextEAGL and GLContextProviderEAGL as an OpenGL provider for iOS. r?jgilbert draft
Ted Mielczarek <ted@mielczarek.org> - Thu, 20 Aug 2015 11:07:59 -0400 - rev 295361
Push 5658 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:19:55 +0000
bug 1174703 - Add GLContextEAGL and GLContextProviderEAGL as an OpenGL provider for iOS. r?jgilbert
40e205057e57e2b75e8d25a2ef89c3ab06e0358c: bug 1171649 - Implement arm/iOS support in JS JITs. r?jandem draft
Ted Mielczarek <ted@mielczarek.org> - Thu, 17 Sep 2015 15:26:11 -0400 - rev 295360
Push 5657 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:15:00 +0000
bug 1171649 - Implement arm/iOS support in JS JITs. r?jandem This patch includes some assembly files from llvm's compiler-rt to implement __aeabi_ividmod and __aeabi_uidivmod.
e6ec9a68e8a937537e5ccb541405e08cc4516236: bug 681602 - Implement xptcall for arm iOS. r?glandium draft
Ted Mielczarek <ted@mielczarek.org> - Tue, 15 Sep 2015 13:54:05 -0400 - rev 295359
Push 5656 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:09:55 +0000
bug 681602 - Implement xptcall for arm iOS. r?glandium The xptinvoke implementation is taken from the arm_openbsd implementation. xptcstubs_arm mostly works on iOS but Apple's assembler is ridiculous so the inline assembly for the SharedStub and the stub methods is just completely #ifdefed.
d955b3538d39ef74c38f49e80965656c94a05adb: bug 1206312 - add IndexedDatabaseManager include to IDBKeyRange. r=bz
Ted Mielczarek <ted@mielczarek.org> - Fri, 18 Sep 2015 20:29:45 -0400 - rev 295358
Push 5656 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:09:55 +0000
bug 1206312 - add IndexedDatabaseManager include to IDBKeyRange. r=bz
986962e1b2e1adc4b705be9e7ffee8603e014a82: bug 1205278 - Use direct_nspr_config for iOS builds. r=glandium
Ted Mielczarek <ted@mielczarek.org> - Wed, 16 Sep 2015 09:01:03 -0400 - rev 295357
Push 5656 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:09:55 +0000
bug 1205278 - Use direct_nspr_config for iOS builds. r=glandium
c18b5ef3be78f7772e056fe386ecef1604f49249: bug 1205273 - Define XP_IOS in js/src. r=glandium
Ted Mielczarek <ted@mielczarek.org> - Tue, 22 Sep 2015 10:51:53 -0400 - rev 295356
Push 5656 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:09:55 +0000
bug 1205273 - Define XP_IOS in js/src. r=glandium
03ac65b27fad56afd0506d066bdab68f6b3660ec: Bug 1205870 - Make sure all possible unboxed array inline capacities are accounted for, r=jandem.
Brian Hackett <bhackett1024@gmail.com> - Tue, 22 Sep 2015 08:59:07 -0600 - rev 295355
Push 5656 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:09:55 +0000
Bug 1205870 - Make sure all possible unboxed array inline capacities are accounted for, r=jandem.
ae935046048083e9f5f859af93fc55588fbc072e: Bug 1168091 - Initialize startLine and startColumn members in FunctionBox constructor, r=jorendorff.
Brian Hackett <bhackett1024@gmail.com> - Tue, 22 Sep 2015 08:54:11 -0600 - rev 295354
Push 5656 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:09:55 +0000
Bug 1168091 - Initialize startLine and startColumn members in FunctionBox constructor, r=jorendorff.
6c84c452a23d74285685bab25f501aac12cd62a8: Bug 1202497 - part 7 - make nsEventQueue use external locking; r=gerald
Nathan Froyd <froydnj@mozilla.com> - Sun, 20 Sep 2015 05:13:09 -0400 - rev 295353
Push 5656 by tmielczarek@mozilla.com at Tue, 22 Sep 2015 16:09:55 +0000
Bug 1202497 - part 7 - make nsEventQueue use external locking; r=gerald We want to ensure that nsThread's use of nsEventQueue uses locking done in nsThread instead of nsEventQueue, for efficiency's sake: we only need to lock once in nsThread, rather than the current situation of locking in nsThread and additionally in nsEventQueue. With the current structure of nsEventQueue, that would mean that nsThread should be using a Monitor internally, rather than a Mutex. Which would be well and good, except that DOM workers use nsThread's mutex to protect their own, internal CondVar. Switching nsThread to use a Monitor would mean that either: - DOM workers drop their internal CondVar in favor of nsThread's Monitor-owned CondVar. This change seems unlikely to work out well, because now the Monitor-owned CondVar is performing double duty: tracking availability of events in nsThread's event queue and additionally whatever DOM workers were using a CondVar for. Having a single CondVar track two things in such a fashion is for Experts Only. - DOM workers grow their own Mutex to protect their own CondVar. Adding a mutex like this would change locking in subtle ways and seems unlikely to lead to success. Using a Monitor in nsThread is therefore untenable, and we would like to retain the current Mutex that lives in nsThread. Therefore, we need to have nsEventQueue manage its own condition variable and push the required (Mutex) locking to the client of nsEventQueue. This scheme also seems more fitting: external clients merely need synchronized access to the event queue; the details of managing notifications about events in the event queue should be left up to the event queue itself. Doing so also forces us to merge nsEventQueueBase and nsEventQueue: there's no way to have nsEventQueueBase require an externally-defined Mutex and then have nsEventQueue subclass nsEventQueueBase and provide its own Mutex to the superclass. C++ initialization rules (and the way things like CondVar are constructed) simply forbid it. But that's OK, because we want a world where nsEventQueue is externally locked anyway, so there's no reason to have separate classes here. One casualty of this work is removing ChaosMode support from nsEventQueue. nsEventQueue had support to delay placing events into the queue, theoretically giving other threads the chance to put events there first. Unfortunately, since the thread would have been holding a lock (as is evident from the MutexAutoLock& parameter required), sleeping in PutEvent accomplishes nothing but delaying the thread from getting useful work done. We should support this, but it's complicated to figure out how to reasonably support this right now. A wrinkle in this overall pleasant refactoring is that nsThreadPool's threads wait for limited amounts of time for new events to be placed in the event queue, so that they can shut themselves down if no new events are appearing. Setting limits on the number of threads also needs to be able to wake up all threads, so threads can shut themselves down if necessary. Unfortunately, with the transition to nsEventQueue managing its own condition variable, there's no way for nsThreadPool to perform these functions, since there's no Monitor to wait on. Therefore, we add a private API for accessing the condition variable and performing the tasks nsThreadPool needs. Prior to all the previous patches, placing items in an nsThread's event queue required three lock/unlock pairs: one for nsThread's Mutex, one to enter nsEventQueue's ReentrantMonitor, and one to exit nsEventQueue's ReentrantMonitor. The upshot of all this work is that we now only require one lock/unlock pair in nsThread itself, as things should be.
(0) -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip