8fb97bb36e55fefaa56dd4058c8286b15172a701: Bug 522353 - nsCategoryCache is still observing category changes after xpcom-shutdown, r=biesi, moa=bsmedberg
Marco Bonardo <mbonardo@mozilla.com> - Thu, 19 Nov 2009 14:15:05 +0100 - rev 35131
Bug 522353 - nsCategoryCache is still observing category changes after xpcom-shutdown, r=biesi, moa=bsmedberg
7385868057d79e69d4618e3285c3f42643a0e2d2: Bug 521889 - browser_461743.js is randomly timing out, r=zeniko
Marco Bonardo <mbonardo@mozilla.com> - Thu, 19 Nov 2009 14:15:01 +0100 - rev 35130
Bug 521889 - browser_461743.js is randomly timing out, r=zeniko
49ed45ddf2e103e2ba5ca0a2736ffea5110279d0: Bug 521802 - mochitest-browser-chrome: browser_459906.js intermittent failure, r=zeniko
Marco Bonardo <mbonardo@mozilla.com> - Thu, 19 Nov 2009 14:13:27 +0100 - rev 35129
Bug 521802 - mochitest-browser-chrome: browser_459906.js intermittent failure, r=zeniko
5008731e77c0f0217150ded6aeb5fe551151122a: Bug 520743 - xpcshell-tests: some Places unit tests fail when 'werror' is on, r=mak
Jae-Seong Lee <lusian@gmail.com> - Thu, 19 Nov 2009 14:13:24 +0100 - rev 35128
Bug 520743 - xpcshell-tests: some Places unit tests fail when 'werror' is on, r=mak
ec6c5808321444ead0b280acba430a40277a6598: Bug 528451 - sessionstore-browser-state-set is not reliable regarding closed windows, r=zeniko
Marco Bonardo <mbonardo@mozilla.com> - Thu, 19 Nov 2009 14:13:21 +0100 - rev 35127
Bug 528451 - sessionstore-browser-state-set is not reliable regarding closed windows, r=zeniko
24ddb9b3d3edb53cebe513b904715b12c88ce9dd: Fixed includes on case sensitive systems. (actually, this time)
Jacek Caban <jacek@codeweavers.com> - Thu, 19 Nov 2009 14:04:44 +0100 - rev 35126
Fixed includes on case sensitive systems. (actually, this time) Bug 501034 - (Packaged) Unit tests boxes should be able to get a stack trace from browser hangs/timeouts. r=ted.mielczarek.
2a7fb310722ee6c6607053f21fb31341aebb9e3e: s/CrLf/Lf/g, EOL whitespace removals.
Serge Gautherie <sgautherie.bz@free.fr> - Thu, 19 Nov 2009 14:01:01 +0100 - rev 35125
s/CrLf/Lf/g, EOL whitespace removals. Bug 501034 - (Packaged) Unit tests boxes should be able to get a stack trace from browser hangs/timeouts; (Dv1). r=ted.mielczarek.
2a0941f8bef93b568801377898b606e75eed8434: Bug 529544 - Avoid creating parser thread when HTML5 parser not enabled. (orange fix)
Henri Sivonen <hsivonen@iki.fi> - Thu, 19 Nov 2009 13:53:32 +0200 - rev 35124
Bug 529544 - Avoid creating parser thread when HTML5 parser not enabled. (orange fix)
21972540dbf42840c7100e7b223ff53fb0b5910f: Merge tracemonkey to mozilla-central.
Robert Sayre <sayrer@gmail.com> - Thu, 19 Nov 2009 11:53:04 +0100 - rev 35123
Merge tracemonkey to mozilla-central.
c84622414ed3321f358722654de84f95fcd78fd3: Merge mozilla-central to tracemonkey.
Robert Sayre <sayrer@gmail.com> - Thu, 19 Nov 2009 09:24:51 +0100 - rev 35122
Merge mozilla-central to tracemonkey.
9a142249a61c7df9d4c42280ca3b2903520c54e0: Merge mozilla-central to tracemonkey.
Robert Sayre <sayrer@gmail.com> - Thu, 19 Nov 2009 02:47:57 +0100 - rev 35121
Merge mozilla-central to tracemonkey.
8dbbc00bb9d81070cd3b777ea85700e84d88b10d: Merge.
Robert Sayre <sayrer@gmail.com> - Thu, 19 Nov 2009 01:23:03 +0100 - rev 35120
Merge.
93db5ba9356c567f8887cb26a582b05df8f2150e: Merge mozilla-central to tracemonkey.
Robert Sayre <sayrer@gmail.com> - Thu, 19 Nov 2009 01:21:34 +0100 - rev 35119
Merge mozilla-central to tracemonkey.
f3b2492321e6c546b81c24b6bcc73bc750648a4e: Fix uninitialized var bug (529679, r=jorendorff).
Brendan Eich <brendan@mozilla.org> - Wed, 18 Nov 2009 15:56:34 -0800 - rev 35118
Fix uninitialized var bug (529679, r=jorendorff).
851d45c347ba5e380ef3c2adc6f2b3b4852c1390: Bug 505523 - Property cache can skip JSClass::resolve or JSClass::addProperty hooks. r=graydon, r=brendan.
Jason Orendorff <jorendorff@mozilla.com> - Wed, 18 Nov 2009 14:29:58 -0600 - rev 35117
Bug 505523 - Property cache can skip JSClass::resolve or JSClass::addProperty hooks. r=graydon, r=brendan.
d7f6d69f6d25eb39a7e2ed77e68da92b719d65b9: Back out ad37dab7ea17: code to check the current frame's script's strictness flag fails the static checks. Using js_GetTopStackFrame introduces a perf regression.
Jim Blandy <jimb@mozilla.org> - Wed, 18 Nov 2009 14:36:55 -0800 - rev 35116
Back out ad37dab7ea17: code to check the current frame's script's strictness flag fails the static checks. Using js_GetTopStackFrame introduces a perf regression.
c73182124eb749c61f544e645b8efdb9e5369ec4: Fix method barrier not to brand, period (branding without reshaping is worse, branding correctly is unnecessary; 524826, r=jorendorff).
Brendan Eich <brendan@mozilla.org> - Wed, 18 Nov 2009 13:41:40 -0800 - rev 35115
Fix method barrier not to brand, period (branding without reshaping is worse, branding correctly is unnecessary; 524826, r=jorendorff).
ad37dab7ea17c88169799192232ff3b5f57800bc: Bug 514585: Machinery for reporting ES5 strict mode errors. r=igor
Jim Blandy <jimb@mozilla.org> - Wed, 18 Nov 2009 13:33:53 -0800 - rev 35114
Bug 514585: Machinery for reporting ES5 strict mode errors. r=igor At compile-time, we must consult the current JSTreeContext to decide whether to issue an strict mode error; at run-time, we need to check the strictness of the currently executing script. Both cases also check the context options. The design is supposed to make it easy to follow the principle that conditions treated as errors in strict mode are a subset of those warned about by JSOPTION_STRICT. This patch removes report flag handling from js_ExpandErrorArguments, which is used for both compile-time and run-time errors. At run-time, the new checkReportFlags handles the checks. At compile-time, we need different checks depending on the situation, so the checks are done in js_ReportStrictModeError, js_ReportCompileErrorNumber, and the new ReportCompileErrorNumberVA.
4559f18f547af4d1e07b0aaa71307f84f1e19e72: Bug 514585: Recognize "use strict" directives. r=igor
Jim Blandy <jimb@mozilla.org> - Wed, 18 Nov 2009 13:33:53 -0800 - rev 35113
Bug 514585: Recognize "use strict" directives. r=igor
486feb450bc9a00f4b19aa62831a4058ef09a242: Bug 514585: Remove macro wrappers for js_NewPrinter and JS_InitArenaPool. r=igor
Jim Blandy <jimb@mozilla.org> - Wed, 18 Nov 2009 13:33:53 -0800 - rev 35112
Bug 514585: Remove macro wrappers for js_NewPrinter and JS_InitArenaPool. r=igor These macros were intended to help avoid passing unused parameters when JS_ARENAMETER is not defined, but they're not worth the trouble. The unused parameter doesn't elicit warnings, and the performance impact of passing the unneeded argument is negligible. This also removes support for JS_ARENA_CONST_ALIGN_MASK, which is not used.
(0) -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip