- 19 May, 2014 15 commits
-
-
machenbach@chromium.org authored
BUG= TBR=jkummerow@chromium.org Review URL: https://codereview.chromium.org/291803005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21368 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dcarney@chromium.org authored
R=verwaest@chromium.org BUG= Review URL: https://codereview.chromium.org/261103002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21366 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
wingo@igalia.com authored
R=jkummerow@chromium.org TBR=rossberg@chromium.org BUG= Review URL: https://codereview.chromium.org/289323005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21365 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
wingo@igalia.com authored
R=rossberg@chromium.org BUG= Review URL: https://codereview.chromium.org/270133003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21362 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
BUG=none R=dcarney@chromium.org LOG=n Review URL: https://codereview.chromium.org/294613002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21361 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
Stores to old space allocations require no write barriers if the object is the new space dominator and the value is not in new space. R=hpayer@chromium.org Review URL: https://codereview.chromium.org/290173003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21360 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
adamk@chromium.org authored
TBR=dcarney@chromium.org Review URL: https://codereview.chromium.org/290313004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21359 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
BUG=374134 LOG=n R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/285193009 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21358 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
adamk@chromium.org authored
TBR=dcarney@chromium.org Review URL: https://codereview.chromium.org/294523006 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21357 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
adamk@chromium.org authored
This avoids the appearence of a leak due to storing a JSObject as the microtask_state in the strong root list, and allows callers to call Isolate::RunMicrotasks() without having any v8::Context available (as at least Blink has interest in doing). The queue is now a strong root, represented as a FixedArray of JSFunctions (or empty_fixed_array, if it's empty); it doubles in size when it needs to grow. The number of elements in the queue is stored in Isolate::pending_microtask_count(). LOG=Y R=dcarney@chromium.org Review URL: https://codereview.chromium.org/290633010 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21356 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
Shamelessly based on parts of https://codereview.chromium.org/288853003/. :-) R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/288383002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21355 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/294543002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21354 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/295543002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21353 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
This reverts the part of r21154 that introduced the CHECK()s to verify state of objects with stable maps during code generation. The CHECK()s seem to trigger a non-critical hidden bug in the map stability mechanism. We will re-add these CHECK()s once the bug is found and fixed. BUG=372173 LOG=y R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/287363002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21352 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
This reverts r21346, it broke the layout tests. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/292713002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21351 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 16 May, 2014 12 commits
-
-
danno@chromium.org authored
R=yangguo@chromium.org LOG=N Review URL: https://codereview.chromium.org/281953002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21348 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
Traditionally, we cross compile a snapshot iff the serializer is enabled. This will change in the future. Changes: - CpuFeatures probing is done once per process, depending on whether we cross compile. - CpuFeatures are consolidated into the platform-independent assembler.h as much as possible. - FLAG_enable_<feature> will only be checked at probing time (already the case for ARM). - The serializer state is cached by the MacroAssembler. - PlatformFeatureScope is no longer necessary. - CPUFeature enum values no longer map to CPUID bit fields. R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/285233010 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21347 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=ulan@chromium.org Review URL: https://codereview.chromium.org/287873005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21346 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
The prologue update in r21329 changed the scoping of the PredictableCodeSizeScope. R=yangguo@chromium.org Review URL: https://codereview.chromium.org/284303003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21345 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
R=yangguo@chromium.org BUG= Review URL: https://codereview.chromium.org/286133002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21344 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
R=yangguo@chromium.org Review URL: https://codereview.chromium.org/286203010 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21343 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
R=dslomov@chromium.org Review URL: https://codereview.chromium.org/283403002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21342 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
Inspired by https://codereview.chromium.org/275143002#msg3 R=machenbach@chromium.org Review URL: https://codereview.chromium.org/290023002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21341 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
R=dslomov@chromium.org Review URL: https://codereview.chromium.org/290513002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21340 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=aandrey@chromium.org, amikhaylova@google.com Review URL: https://codereview.chromium.org/283373003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21339 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/284283005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21338 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
m.m.capewell@googlemail.com authored
CPUFeatures::Probe has been modified such that it can be called only once, but the cctests make two calls in native builds: once in VM init, and once in each test setup. This patch removes the call in the test setup. BUG= R=ulan@chromium.org Review URL: https://codereview.chromium.org/285273003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21337 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 15 May, 2014 13 commits
-
-
machenbach@chromium.org authored
Drain the queues to prevent failures when queues are garbage collected. Fails when interrupting test262 otherwise. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/286973004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21334 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
This fixes JSObject::GetCreationContext() for such iterators. R=rossberg@chromium.org Review URL: https://codereview.chromium.org/288233002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21333 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
Specifically: DataView{S,G}et* and a few more Math functions. Also change indentation in typedarray.js for easier future builtins parsing. R=dslomov@chromium.org Review URL: https://codereview.chromium.org/286073004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21332 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=machenbach@chromium.org Review URL: https://codereview.chromium.org/288163003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21331 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
Use the same keyboard interrupt logic as run-tests. Close the perf database explicitly after one run, as it has two runs on the same architecture. Currently the first run closes on garbage collection, which might corrupt the second run. BUG= R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/284203002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21330 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=titzer@chromium.org Review URL: https://codereview.chromium.org/288213002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21329 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
BUG= R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/273613005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21328 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
hpayer@chromium.org authored
BUG= R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/282223005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21327 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
hpayer@chromium.org authored
BUG= R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/289973002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21326 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=ulan@chromium.org Review URL: https://codereview.chromium.org/289473005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21325 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
marja@chromium.org authored
In some places, we pretended that there can be multiple arguments, though in practice there was only one. In other places (most importantly, PreParser), we only handled one argument. (This means that we were not able to produce a multi-argument error inside a lazy function anyway.) This CL makes it clear that there is ever only one argument. R=ulan@chromium.org BUG= Review URL: https://codereview.chromium.org/273653002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21324 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/290453004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21323 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/285333002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21322 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-