- 16 Jul, 2014 9 commits
-
-
rossberg@chromium.org authored
R=mstarzinger@chromium.org BUG=v8:3442 LOG=Y Review URL: https://codereview.chromium.org/389263003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22426 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
The current gyp config tries to test whether the compiler is an arm / mips compiler and whether it supports -m32 / -m64 based on a test within gyp. Unfortunately CXX / CXX_target / CXX_host are no no longer set early enough in gyp for this to work, and so all of these tests were actually being done using "$(which g++)" rather than the appropriate CXX_target / CXX_host compiler. This change removes these dynamic tests and instead bases the decisions on knowledge of the host / target / v8_target architecture combination. The the -m32/-m64 flags are set based on host_cxx_is_biarch / target_cxx_is_biarch, which are set to reasonable defaults of only ia32/x64 or clang compilers being build for biarch support. The host_cxx_is_biarch / target_cxx_is_biarch variables can be overriden if required. BUG=384474 LOG=NO R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/382343003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22425 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
Some benchmarks include their own runner which provides an overall average and a standard deviation. This enables extraction of that value similar to the other measurements. These benchmarks should only be run once. If a benchmarks specifies multiple runs and provides a standard deviation, a warning will be issued that makes the build fail on the buildbot side. TEST=python -m unittest run_benchmarks_test BUG=393947 LOG=n R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/395633012 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22424 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/394153003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22423 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=fmeawad@chromium.org Review URL: https://codereview.chromium.org/388783004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22422 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
The version.cc file will from now on be controlled on bleeding edge and on trunk. The next version to use will always be max(bleeding_edge_version, trunk_version) + 1. The trunk and bleeding_edge versions are not semantically tied together. The trunk branch can be used to make independent point releases of bleeding_edge revisions. The version on bleeding_edge will be increased if: - the lkgr version is smaller than the version of the latest revision, - the lkgr version is not a version change itself, - the tree is not closed for maintenance. This will allow chromium to refer directly to bleeding_edge revisions of v8. The v8 versions will not be unique, but they will change as often as possible, dependent on the lkgr cycle time and the frequency this script is called. BUG=391261 LOG=n TEST=tools/push-to-trunk/script_test.py TEST=tools/push-to-trunk/bump_up_version.py --dry_run R=jarin@chromium.org Review URL: https://codereview.chromium.org/389353003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22421 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=verwaest@chromium.org BUG=393988 LOG=N Review URL: https://codereview.chromium.org/396063008 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22420 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=mvstanton@chromium.org, vogelheim@chromium.org Review URL: https://codereview.chromium.org/394793002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22417 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
weiliang.lin@intel.com authored
port r22391 original commit message: Drop unnecessary receiver validity checks from {Load,Store}IC_Normal. Since these builtins are used as handlers after a map check/dispatch, they don't need to check the receiver again. BUG= R=weiliang.lin@intel.com Review URL: https://codereview.chromium.org/396833004 Patch from Chunyang Dai <chunyang.dai@intel.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22416 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 15 Jul, 2014 22 commits
-
-
akos.palfi@imgtec.com authored
BUG= R=akos.palfi@imgtec.com Review URL: https://codereview.chromium.org/394913002 Patch from Balazs Kilvady <kilvadyb@homejinni.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22413 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
akos.palfi@imgtec.com authored
BUG= R=akos.palfi@imgtec.com Review URL: https://codereview.chromium.org/395863002 Patch from Balazs Kilvady <kilvadyb@homejinni.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22412 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
akos.palfi@imgtec.com authored
Port r22391 (fe86010) Original commit message: Since these builtins are used as handlers after a map check/dispatch, they don't need to check the receiver again. BUG= R=akos.palfi@imgtec.com Review URL: https://codereview.chromium.org/396663004 Patch from Balazs Kilvady <kilvadyb@homejinni.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22411 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dusan.milosavljevic@rt-rk.com authored
Port r22129 (676bb14). TEST= BUG= R=balazs.kilvady@imgtec.com, paul.lind@imgtec.com Review URL: https://codereview.chromium.org/395803002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22410 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
hpayer@chromium.org authored
TBR=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/398473002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22409 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
hpayer@chromium.org authored
BUG= R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/397613002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22408 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/390353002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22407 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=yangguo@chromium.org BUG=v8:2803 LOG=N Review URL: https://codereview.chromium.org/395713002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22406 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
weiliang.lin@intel.com authored
port r22387 original commit message: Use the same registers for StoreIC and KeyedStoreIC. Based on https://codereview.chromium.org/389283002 ("Use register parameters in ElementsTransitionGenerator") which must land first. BUG= R=weiliang.lin@intel.com Review URL: https://codereview.chromium.org/391933002 Patch from Chunyang Dai <chunyang.dai@intel.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22405 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mvstanton@chromium.org authored
"Info" is information-poor. R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/385953004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22404 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/390303002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22403 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
weiliang.lin@intel.com authored
port r22384 original commit message: Use register parameters in ElementsTransitionGenerator x BUG= R=weiliang.lin@intel.com Review URL: https://codereview.chromium.org/395633010 Patch from Chunyang Dai <chunyang.dai@intel.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22402 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=yangguo@chromium.org BUG=v8:2803 LOG=N Review URL: https://codereview.chromium.org/390193007 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22399 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/387343002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22398 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
akos.palfi@imgtec.com authored
Port r22387 (ff76c666) BUG= R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/390263002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22397 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
akos.palfi@imgtec.com authored
Port r22384 (52caca20) BUG= R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/393693003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22396 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
weiliang.lin@intel.com authored
port r22379 original commit message: This CL simplifies var / const by ensuring the behavior is consistent in itself, and with regular JS semantics; between regular var/const and eval-ed var/const. Legacy const is changed so that a declaration declares a configurable, but non-writable, slot, and the initializer reconfigures it (when possible) to non-configurable non-writable. This avoids the need for "the hole" as marker value in JSContextExtensionObjects and GlobalObjects. Undefined is used instead. BUG= R=weiliang.lin@intel.com Review URL: https://codereview.chromium.org/397573002 Patch from Chunyang Dai <chunyang.dai@intel.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22395 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
hpayer@chromium.org authored
BUG= R=jarin@chromium.org Review URL: https://codereview.chromium.org/396443004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22394 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
danno@chromium.org authored
During https://code.google.com/p/v8/source/detail?r=19925 checkin context bound scripts (Script) and context unbound scripts (UnboundScript) are Distinguished. And then Sven Panne helped to fix the vtune support compilation error in https://code.google.com/p/v8/source/detail?r=20955. The problem is that there is runtime error for vtune support. In our original implementation, we encapsulated and passed v8::internal::Script to V8 API. It will leads to type check error for current V8::Script definition. So I changed the Handle<Script> definition in JitCodeEvent to Handle<UnboundScript> and add the corresponding change in log.cc. If you do NOT prefer to change in include/v8.h. I think I can change the definition of CodeEventLogger::LogRecordedBuffer(...) so that the we can pass the correct type (JSFunction) as V8::Script to V8 API. BUG= R=danno@chromium.org, svenpanne@chromium.org Review URL: https://codereview.chromium.org/334263018 Patch from Chunyang Dai <chunyang.dai@intel.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22393 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
marja@chromium.org authored
There are a lot of tests in cctest/test-parsing/ErrorsArrowFunctions, so it is quite slow. This patch removes some flags to make it faster. Removing three flags that don't affect the test brings down the run time one order of magnitude, which is fast enough even for debug/ASAN bots. Also, remove the unneeded kArrowFunctions flag from cctest/test-parsing/NoErrorsYieldSloppyAllModes BUG= R=marja@chromium.org Review URL: https://codereview.chromium.org/387383002 Patch from Adrián Pérez de Castro <aperez@igalia.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22392 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
Since these builtins are used as handlers after a map check/dispatch, they don't need to check the receiver again. R=verwaest@chromium.org Review URL: https://codereview.chromium.org/390053002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22391 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
BUG=v8:3436 LOG=y R=dcarney@chromium.org Review URL: https://codereview.chromium.org/388183002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22390 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 14 Jul, 2014 9 commits
-
-
mvstanton@chromium.org authored
Based on https://codereview.chromium.org/389283002 ("Use register parameters in ElementsTransitionGenerator") which must land first. R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/390013002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22387 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kilvadyb@homejinni.com authored
Port r22382 (84a841f) BUG= R=akos.palfi@imgtec.com Review URL: https://codereview.chromium.org/395503002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22386 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kilvadyb@homejinni.com authored
MIPS: This CL simplifies var / const by ensuring the behavior is consistent in itself, and with regular JS semantics; between regular var/const and eval-ed var/const. Port r22379 (fb62653) Original commit message: Legacy const is changed so that a declaration declares a configurable, but non-writable, slot, and the initializer reconfigures it (when possible) to non-configurable non-writable. This avoids the need for "the hole" as marker value in JSContextExtensionObjects and GlobalObjects. Undefined is used instead. BUG= R=akos.palfi@imgtec.com Review URL: https://codereview.chromium.org/389373004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22385 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mvstanton@chromium.org authored
R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/389283002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22384 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
verwaest@chromium.org authored
BUG= R=ishell@chromium.org Review URL: https://codereview.chromium.org/390833003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22383 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
verwaest@chromium.org authored
BUG= R=rossberg@chromium.org Review URL: https://codereview.chromium.org/385173009 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22382 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
verwaest@chromium.org authored
BUG= R=ishell@chromium.org Review URL: https://codereview.chromium.org/384003003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22381 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
R=yangguo@chromium.org Review URL: https://codereview.chromium.org/388243002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22380 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
verwaest@chromium.org authored
This CL simplifies var / const by ensuring the behavior is consistent in itself, and with regular JS semantics; between regular var/const and eval-ed var/const. Legacy const is changed so that a declaration declares a configurable, but non-writable, slot, and the initializer reconfigures it (when possible) to non-configurable non-writable. This avoids the need for "the hole" as marker value in JSContextExtensionObjects and GlobalObjects. Undefined is used instead. BUG= R=rossberg@chromium.org Review URL: https://codereview.chromium.org/379893002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22379 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-