- 10 Mar, 2017 11 commits
-
-
Georg Neis authored
The callers of this function already do the flushing (as its comment demands). BUG= Change-Id: Iff6720f4ddecb1a4569b6cac66eba4b857c46b17 Reviewed-on: https://chromium-review.googlesource.com/452504Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#43718}
-
Camillo Bruni authored
- lower the cutoff-threshold for bottom up graphs to 1% - show all builtins/stubs/ics by default R=jkummerow@chromium.org Change-Id: I522173155b817ae20a37c40ecf411f2b55d82105 Reviewed-on: https://chromium-review.googlesource.com/452482Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#43717}
-
wiktorg authored
BUG= R=marja@chromium.org Review-Url: https://codereview.chromium.org/2738153003 Cr-Commit-Position: refs/heads/master@{#43716}
-
Michael Lippautz authored
BUG= Change-Id: Icfc5412316279bed6cc95107303fbee6be66ebb4 Reviewed-on: https://chromium-review.googlesource.com/452618Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#43715}
-
yangguo authored
R=clemensh@chromium.org, jgruber@chromium.org BUG=v8:5530 Review-Url: https://codereview.chromium.org/2727393003 Cr-Commit-Position: refs/heads/master@{#43714}
-
yangguo authored
This is clearly a case of "nuke later" where later means now. R=mlippautz@chromium.org BUG=v8:6072 Review-Url: https://codereview.chromium.org/2741723002 Cr-Commit-Position: refs/heads/master@{#43713}
-
yangguo authored
BUG=v8:6072 Review-Url: https://codereview.chromium.org/2741573003 Cr-Commit-Position: refs/heads/master@{#43712}
-
bmeurer authored
Add log message when RuntimeProfiler checks whether to optimize a function, but that function is already in the optimization queue (with --trace-opt-verbose). R=yangguo@chromium.org Review-Url: https://codereview.chromium.org/2740103003 Cr-Commit-Position: refs/heads/master@{#43711}
-
yangguo authored
R=caseq@chromium.org, pfeldman@chromium.org BUG=v8:5808 Review-Url: https://codereview.chromium.org/2741653003 Cr-Commit-Position: refs/heads/master@{#43710}
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/33b29e1..957a0ba Rolling v8/third_party/catapult: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+log/38ed490..2ae07fc Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/e96a7b4..61f0bb2 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Change-Id: I24ee3abd981a32f76a2eba47935e8ac0a5f9203e Reviewed-on: https://chromium-review.googlesource.com/452322Reviewed-by: v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#43709}
-
jing.bao authored
CreateInt32x4, Int32x4ExtractLane, Int32x4ReplaceLane Int32x4Add, Int32x4Sub Also add paddd, psubd, vpaddd, vpsubd, pinsrw to ia32-assembler BUG= Review-Url: https://codereview.chromium.org/2695613004 Cr-Original-Commit-Position: refs/heads/master@{#43483} Committed: https://chromium.googlesource.com/v8/v8/+/4deb9ffdecf121c69a3db7eae6698eae23a80a15 Review-Url: https://codereview.chromium.org/2695613004 Cr-Commit-Position: refs/heads/master@{#43708}
-
- 09 Mar, 2017 27 commits
-
-
jshin authored
ICU's UChar was uint16_t (non-Win) or wchar_t (Windows). It's switching to char16_t in both C/C++ API. It needs some changes. Fortunately, v8 needs only a couple of changes because v8 has been using reinterpret_cast in many places calling ICU API. This change was confirmed to work fine with ICU-59-to-be. BUG=v8:6062 TEST=trybot Review-Url: https://codereview.chromium.org/2738503008 Cr-Commit-Position: refs/heads/master@{#43707}
-
Camillo Bruni authored
Chrome no longer calls v8::Isolate::Dispose on shutdown, essentially preventing the use of V8 stats within chrome/content_shell. This CL adds a basic hook to the api that is then used to only print the stats. Chrome change: https://codereview.chromium.org/2693353002 Change-Id: I1481c14afe611e9c08ae67c815201a45940daa57 Reviewed-on: https://chromium-review.googlesource.com/452338Reviewed-by: Jochen Eisinger <jochen@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#43706}
-
Camillo Bruni authored
This reverts commit 8cebe1cc. Reason for revert: Failing ticksprocessor tests Original change's description: > [tools] Show more entries in the ticks-processor > > - lower the cutoff-threshold for bottom up graphs to 1% > - show all builtins/stubs/ics by default > > R=jkummerow@chromium.org > > Change-Id: I85f8c4f00c5f36407bc5d9f81bead8f39a5ef632 > > NOTRY=true > > Change-Id: I85f8c4f00c5f36407bc5d9f81bead8f39a5ef632 > Reviewed-on: https://chromium-review.googlesource.com/452300 > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Commit-Queue: Camillo Bruni <cbruni@chromium.org> > Cr-Commit-Position: refs/heads/master@{#43704} TBR=jkummerow@chromium.org,cbruni@chromium.org,v8-reviews@googlegroups.com NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Change-Id: I4e911778eebcaebaab6658f2956c9fb7c35d0ee3 Reviewed-on: https://chromium-review.googlesource.com/452339Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#43705}
-
Camillo Bruni authored
- lower the cutoff-threshold for bottom up graphs to 1% - show all builtins/stubs/ics by default R=jkummerow@chromium.org Change-Id: I85f8c4f00c5f36407bc5d9f81bead8f39a5ef632 NOTRY=true Change-Id: I85f8c4f00c5f36407bc5d9f81bead8f39a5ef632 Reviewed-on: https://chromium-review.googlesource.com/452300Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#43704}
-
yangguo authored
R=ishell@chromium.org BUG=v8:6073 Review-Url: https://codereview.chromium.org/2737373003 Cr-Commit-Position: refs/heads/master@{#43703}
-
sreten.kovacevic authored
Port 040fa762 TEST=cctest/test-run-machops/Regression6046b BUG= Review-Url: https://codereview.chromium.org/2742773002 Cr-Commit-Position: refs/heads/master@{#43702}
-
Michael Achenbach authored
BUG=chromium:682617 R=mstarzinger@chromium.org,bmeurer@chromium.org Change-Id: I1dedc4e2a0cb6e5e42b734c7eb99a40164da4229 Reviewed-on: https://chromium-review.googlesource.com/452498 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#43701}
-
danno authored
Specifically, add bytecodes for Call0, Call1, Call2, CallProperty0, CallProperty1, and CallProperty2. Also share the bytecode handler code between between equivalent CallX and CallPropertyX handlers. Review-Url: https://codereview.chromium.org/2684993002 Cr-Original-Commit-Position: refs/heads/master@{#43290} Committed: https://chromium.googlesource.com/v8/v8/+/00d6f1f80a00c4ac398af588dbd6815395791015 Review-Url: https://codereview.chromium.org/2684993002 Cr-Commit-Position: refs/heads/master@{#43700}
-
bmeurer authored
The optimization NumberFloor(NumberDivide(lhs, rhs)) to NumberToInt32(NumberDivide(lhs, rhs)) for potentially negative lhs is not valid, since Math.floor rounds towards -infinity, whereas ToInt32 truncates. BUG=chromium:699282 R=jarin@chromium.org Review-Url: https://codereview.chromium.org/2743673002 Cr-Commit-Position: refs/heads/master@{#43699}
-
yangguo authored
We used to embed a string address as description right after a stop instruction, which the simulator would read and print. We removed that a while ago to make the snapshot predictable. R=petermarshall@chromium.org BUG=v8:6071 Review-Url: https://codereview.chromium.org/2744503003 Cr-Commit-Position: refs/heads/master@{#43698}
-
yangguo authored
R=vogelheim@chromium.org BUG=v8:6072 Review-Url: https://codereview.chromium.org/2738213002 Cr-Commit-Position: refs/heads/master@{#43697}
-
Michael Lippautz authored
We need to check whether advancing the iterator moved us beyong the end of the bitmap. This has not been flushed out as our inlined bitmap is still in valid memory. In practice this is not a problem because the value is never used as we are at the end of the bitmap. Asan rightfully complains when using an external bitmap though. BUG=chromium:651354 Change-Id: I8b141a467e9552f8ac2287dd62a725a14a289a37 Reviewed-on: https://chromium-review.googlesource.com/452497Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#43696}
-
jkummerow authored
Review-Url: https://codereview.chromium.org/2734323004 Cr-Commit-Position: refs/heads/master@{#43695}
-
Michael Achenbach authored
BUG=chromium:682617 NOTRY=true R=mvstanton@chromium.org,petermarshall@chromium.org Change-Id: I5902c4ac3c8fb4230142896addbb75a9e7d28fbb Reviewed-on: https://chromium-review.googlesource.com/451378Reviewed-by: Michael Stanton <mvstanton@chromium.org> Reviewed-by: Peter Marshall <petermarshall@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#43694}
-
Igor Sheludko authored
BUG=v8:5495 Change-Id: I731ddaa34169f6f57d3719e6170bfe00e6d66241 Reviewed-on: https://chromium-review.googlesource.com/451638 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#43693}
-
yangguo authored
And a drive-by clean up of unused flag. R=jgruber@chromium.org BUG=v8:5530 Review-Url: https://codereview.chromium.org/2744553002 Cr-Commit-Position: refs/heads/master@{#43692}
-
Igor Sheludko authored
BUG=chromium:686010 Change-Id: I7bd4ab48f90a1013132bf037fd352ab55747189c Reviewed-on: https://chromium-review.googlesource.com/451377 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#43691}
-
yangguo authored
R=ishell@chromium.org BUG=v8:6071 Review-Url: https://codereview.chromium.org/2740073002 Cr-Commit-Position: refs/heads/master@{#43690}
-
Georg Neis authored
BUG= Change-Id: Ibf49df830153a829015723826dacc6939fb42189 Reviewed-on: https://chromium-review.googlesource.com/452377Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#43689}
-
yangguo authored
We actually do want to make changes in debug-evaluate stick. R=jgruber@chromium.org BUG=v8:6071 Review-Url: https://codereview.chromium.org/2743613002 Cr-Commit-Position: refs/heads/master@{#43688}
-
Igor Sheludko authored
It depends on constant field tracking and currently disabled. BUG=v8:5495 Change-Id: I6202cddfc2d32b5a06c5ab00c42caa6e276a3eb1 Reviewed-on: https://chromium-review.googlesource.com/451639 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#43687}
-
jgruber authored
This fixes an incorrect usage of String::Flatten in EscapeRegExpSource. It also adds %ConstructConsString (to easily and reliably construct cons strings in tests) and Factory::NewConsString (to enable guaranteed cons string construction without preemptive flattening attempts). BUG=chromium:698790 Review-Url: https://codereview.chromium.org/2736383003 Cr-Commit-Position: refs/heads/master@{#43686}
-
Camillo Bruni authored
- supporting appending new data instead of simply replacing the current set - fix issue when not filtering out groups on initial loading Change-Id: I77d508e644b247fa236ea64ef919639cac6ee425 NOTRY=true Change-Id: I77d508e644b247fa236ea64ef919639cac6ee425 Reviewed-on: https://chromium-review.googlesource.com/451276 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#43685}
-
mvstanton authored
_____ _ _ _ |_ _| (_) | (_) | | __ _ _ __ _| |_ _ ___ _ __ | | / _` | '_ \| | __| |/ _ \| '_ \ _| || (_| | | | | | |_| | (_) | | | | \___/\__, |_| |_|_|\__|_|\___/|_| |_| __/ | |___/ _ _| |_ |_ _| |_| _____ _ ______ |_ _| | | | ___| | |_ _ _ __| |__ ___ | |_ __ _ _ __ | | | | | '__| '_ \ / _ \| _/ _` | '_ \ | | |_| | | | |_) | (_) | || (_| | | | | \_/\__,_|_| |_.__/ \___/\_| \__,_|_| |_| BUG=v8:5267, v8:4280, chromium:692409 NOTREECHECKS=true Review-Url: https://codereview.chromium.org/2736723006 Cr-Original-Commit-Position: refs/heads/master@{#43663} Committed: https://chromium.googlesource.com/v8/v8/+/e7f8575851a0a56ffe6772d98fd8d90602e6876b Review-Url: https://codereview.chromium.org/2736723006 Cr-Commit-Position: refs/heads/master@{#43684}
-
bmeurer authored
The BitcastWordToTagged operator is used for bump pointer allocation to construct the actual HeapObject pointer. The input to this operator is a naked pointer (derived from the allocation top). If this input value is live across an allocation, then the resulting tagged pointer is invalid because the GC might have scavenged new space in the meantime. That means we must not allow Node splitting (in the Scheduler) for these instructions, as that could extend the live range of the naked pointer input across arbitrary code. As such, this operator must not be marked as pure. R=jarin@chromium.org BUG=v8:6059 Review-Url: https://codereview.chromium.org/2739093002 Cr-Commit-Position: refs/heads/master@{#43683}
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/5f4c2a0..33b29e1 Rolling v8/third_party/catapult: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+log/299d02a..38ed490 Rolling v8/third_party/instrumented_libraries: https://chromium.googlesource.com/chromium/src/third_party/instrumented_libraries/+log/e905e0f..6227538 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Change-Id: If7cb4e575b769ba2154845c421a5d6b30b9b8ecd Reviewed-on: https://chromium-review.googlesource.com/452157Reviewed-by: v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#43682}
-
bbudge authored
- Changes input filtering to test NaNs, but skip very large or very small inputs, which may cause imprecision on some platforms. - Changes expected result filtering to only skip NaNs. LOG=N BUG=6020 Review-Url: https://codereview.chromium.org/2738703006 Cr-Commit-Position: refs/heads/master@{#43681}
-
- 08 Mar, 2017 2 commits
-
-
bjaideep authored
Port 301c1237 R=binji@chromium.org, aseemgarg@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG=v8:4614 LOG=N Review-Url: https://codereview.chromium.org/2733953004 Cr-Commit-Position: refs/heads/master@{#43680}
-
hpayer authored
BUG=chromium:694255 Review-Url: https://codereview.chromium.org/2492263002 Cr-Commit-Position: refs/heads/master@{#43679}
-