Context Navigation

Search

Results (81 - 90 of 304)

← 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 →

[152871]: Fixed ASSERTION FAILED: callFrame == vm->topCallFrame in ...: ... 5_String/15.5.4/15.5.4.8_String.prototype.lastIndexOf/S15.5.4.8_A7-expected.txt: * svg/custom/createelement-expected.txt: * svg/custom/use-nested-missing-target-removed-expected.txt: * svg/dom/svgpath-out-of-bounds-getPathSeg-expected.txt:; By commit-queue@webkit.org — Jul 18, 2013, 4:24:13 PM
[152280]: [JSC]: Fix maybe-uninitialized gcc 4.8 warning in ...: [JSC]: Fix maybe-uninitialized gcc 4.8 warning in DFGSpeculativeJIT.cpp https://bugs.webkit.org/show_bug.cgi?id=118278 Patch by Sergio Correia <sergio.correia@openbossa.org> on 2013-07-01 Reviewed by Filip Pizlo. * dfg/DFGSpeculativeJIT.cpp: (JSC::DFG::SpeculativeJIT::comp ...; By commit-queue@webkit.org — Jul 1, 2013, 11:03:12 PM
[151363]: Re-worked non-local variable resolution ...: ... 5_String/15.5.4/15.5.4.8_String.prototype.lastIndexOf/S15.5.4.8_A1_T3-expected.txt: Updated to show failing results. Firefox and Chrome also fail these tests, and the ES5 spec seems to mandate failure. Because these tests resolve a String.prototype function at ...; By ggaren@apple.com — Jun 9, 2013, 10:45:15 PM
[150513]: WebCore fails to compile with -Werror=maybe-uninitialized on GCC 4.8.0 ...: ... maybe-uninitialized on GCC 4.8.0 https://bugs.webkit.org/show_bug.cgi?id=116340 Reviewed by Christophe Dumez. No new tests, just a simple build fix. * inspector/InspectorDOMStorageAgent.cpp: (WebCore::InspectorDOMStorageAgent::setDOMStorageItem): Init frame variab ...; By Hugo Parente Lima — May 22, 2013, 6:45:15 AM
[149962]: Merge r147640 - Fix the build with GCC 4.8 ...: Merge r147640 - Fix the build with GCC 4.8 https://bugs.webkit.org/show_bug.cgi?id=113147 Reviewed by Allan Sandfeld Jensen. Source/JavaScriptCore: Initialize JSObject* exception to suppress warnings that make the build fail because of -Werror=maybe-uninitialized. * runtime/ ...; By Carlos Garcia Campos — May 12, 2013, 9:33:15 AM
[149622]: Build with GCC 4.8 fails because of -Wmaybe-uninitialized ...: Build with GCC 4.8 fails because of -Wmaybe-uninitialized https://bugs.webkit.org/show_bug.cgi?id=115648 Reviewed by Michael Saboff. Initialize values in Options::setOption since from there we end up calling OptionRange::init with uninitialized members. ...; By abecsi@webkit.org — May 6, 2013, 11:49:10 AM
[149527]: Rationalized 'this' value conversion ...: ... 5_String/15.5.4/15.5.4.8_String.prototype.lastIndexOf/S15.5.4.8_A1_T3-expected.txt:; By ggaren@apple.com — May 3, 2013, 11:46:45 AM
[148070]: [CSS3] Parsing the property, text-justify. ...: ... * platform/mac/TestExpectations: ditto * platform/qt-4.8/TestExpectations: ditto * platform/qt-mac/TestExpectations: ditto * platform/qt/TestExpectations: ditto; By dw.im@samsung.com — Apr 9, 2013, 5:32:39 PM
[147922]: Fix the build with strict GCC 4.8 Unreviewed build fix. Initialize ...: Fix the build with strict GCC 4.8 Unreviewed build fix. Initialize dragImage to suppress GCC's warning about it being possibly used uninitialized, which results is a build failure with GCC 4.8 that sets -Werror=maybe-uninitialized. No new tests needed. * page/DragCo ...; By abecsi@webkit.org — Apr 8, 2013, 10:04:30 AM
[147640]: Fix the build with GCC 4.8 ...: Fix the build with GCC 4.8 https://bugs.webkit.org/show_bug.cgi?id=113147 Reviewed by Allan Sandfeld Jensen. Source/JavaScriptCore: Initialize JSObject* exception to suppress warnings that make the build fail because of -Werror=maybe-uninitialized. * runtime/ ...; By abecsi@webkit.org — Apr 4, 2013, 9:40:41 AM

← 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 →

Note: See TracSearch for help on searching.