- 12 Aug, 2014 1 commit
-
-
dusan.milosavljevic@imgtec.com authored
Fixing gclient runhooks failure caused by reverted commit r23050. TEST= BUG= R=jkummerow@chromium.org, paul.lind@imgtec.com Review URL: https://codereview.chromium.org/467583002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23088 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 11 Aug, 2014 6 commits
-
-
machenbach@chromium.org authored
This reverts commit r23052. This sets a new landmine. TBR=jochen@chromium.org BUG=400033 LOG=n Review URL: https://codereview.chromium.org/465583002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23054 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
This reverts commit r23050 for breaking runhooks on chromium. See e.g.: http://build.chromium.org/p/client.v8/builders/Chrome%20Linux%20Perf/builds/1438/steps/runhooks/logs/stdio TBR=jochen@chromium.org Review URL: https://codereview.chromium.org/458983003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23053 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
This also adds a landmine as windows bots need a clobber. BUG=400033 LOG=n TBR=svenpanne@chromium.org Review URL: https://codereview.chromium.org/457413003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23052 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dusan.milosavljevic@imgtec.com authored
Original commit r23028 breaks ARM64 build due to conflicting FP64 symbolic constant definition in src/globals.h and src/arm64/constants-arm64.h. TEST= BUG= R=jkummerow@chromium.org, paul.lind@imgtec.com Review URL: https://codereview.chromium.org/457313003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23050 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
Breaks compilation of ARM64. | Additional summary: | - Introduce fp64 fpu mode into mips32 port required for r6. | - Implement runtime detections for fpu mode and arch. revision to preserve | compatibility with previous architecture revisions. | | TEST= | BUG= | R=jkummerow@chromium.org, paul.lind@imgtec.com | | Review URL: https://codereview.chromium.org/453043002 BUG=none LOG=n TBR=jkummerow@chromium.org Review URL: https://codereview.chromium.org/458193002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23030 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dusan.milosavljevic@imgtec.com authored
Additional summary: - Introduce fp64 fpu mode into mips32 port required for r6. - Implement runtime detections for fpu mode and arch. revision to preserve compatibility with previous architecture revisions. TEST= BUG= R=jkummerow@chromium.org, paul.lind@imgtec.com Review URL: https://codereview.chromium.org/453043002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23028 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Aug, 2014 1 commit
-
-
machenbach@chromium.org authored
Currently, some builders are in a clobber-landmine loop. Clobber deletes the .landmines tracker (sigh). Difficult to know if we are right after a clobber or if it is first-time landmines deployment. Also, a landmine-triggered clobber right after a clobber is not possible. Different clobber methods for msvs, xcode and make all have different blacklists of files that are not deleted. After the branch point, all v8 branch builders have to be manually clobbered, because the appearance of the landmines.py script and the first landmine request are in the same branch CL. TBR=jochen@chromium.org Review URL: https://codereview.chromium.org/457063002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23012 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 08 Aug, 2014 2 commits
-
-
machenbach@chromium.org authored
TBR=jochen@chromium.org Review URL: https://codereview.chromium.org/452903004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23006 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
LOG=y BUG=v8:3489 R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/457503002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22987 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 06 Aug, 2014 3 commits
-
-
bmeurer@chromium.org authored
This reverts commit r22927 for breaking build. TBR=svenpanne@chromium.org Review URL: https://codereview.chromium.org/448663002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22928 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
TEST=compiler-unittests BUG=v8:3489 LOG=y R=svenpanne@chromium.org, jochen@chromium.org Review URL: https://codereview.chromium.org/447563003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22927 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
TEST=base-unittests BUG=v8:3489 LOG=y R=jochen@chromium.org, svenpanne@chromium.org Review URL: https://codereview.chromium.org/448603002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22911 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 05 Aug, 2014 5 commits
-
-
bmeurer@chromium.org authored
This reverts commit r22878 and fixes the actual bug instead. R=hpayer@chromium.org Review URL: https://codereview.chromium.org/446573002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22880 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
It's unclear whether it's a clang bug or our code is wrong, to be verified later... TBR=bmeurer@chromium.org Review URL: https://codereview.chromium.org/438323002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22878 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
* Consistently enable C++11 features on all platforms. * Use the same ARM toolchain version as Chrome. * Make clang the default on Mac OS X, just like Chrome. * Use C99 on Mac OS X, again following Chrome. * Small build fixes. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/440663002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22875 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
This reverts commit r22847 and r22848. Isolate initialization/shutdown still broken (so certain debug builds just crash), and our compiler flags do not work with other Google projects (i.e. GTest/GMock). TBR=jochen@chromium.org Review URL: https://codereview.chromium.org/438243003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22855 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
R=jochen@chromium.org, svenpanne@chromium.org Review URL: https://codereview.chromium.org/439863004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22847 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 01 Aug, 2014 1 commit
-
-
danno@chromium.org authored
R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/432863002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22779 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 30 Jul, 2014 1 commit
-
-
danno@chromium.org authored
R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/426233002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22709 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 29 Jul, 2014 2 commits
-
-
dusan.milosavljevic@imgtec.com authored
TEST= BUG= R=jkummerow@chromium.org, paul.lind@imgtec.com Review URL: https://codereview.chromium.org/426863006 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22681 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
danno@chromium.org authored
BUG= R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/424763002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22675 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 23 Jul, 2014 3 commits
-
-
machenbach@chromium.org authored
Tests only the default variant for now. BUG= R=jochen@chromium.org Review URL: https://codereview.chromium.org/412853002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22561 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
BUG= R=jochen@chromium.org TBR=jochen@chromium.org Review URL: https://codereview.chromium.org/415533003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22560 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
With the original script, landmines don't work if the initial commit of the landmine script and the first landmine are in the same build. In this case, the landmine file wouldn't exist yet and no landmine would be triggered. But the updated landmine content would have still been written, omitting the landmine. Now, the script will initialize an empty landmine file if none exists. This will make sure that a landmine is set on the branch builders after the next branch point. This also adds some debugging output to better trace when landmines are set/deleted. BUG= R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/410893002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22557 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 22 Jul, 2014 2 commits
-
-
machenbach@chromium.org authored
BUG= TBR=jochen@chromium.org Review URL: https://codereview.chromium.org/412513002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22530 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
The scripts are copied from chromium/src/build and simplified. BUG= R=jkummerow@chromium.org, jochen@chromium.org Review URL: https://codereview.chromium.org/405373005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22529 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 18 Jul, 2014 3 commits
-
-
rmcilroy@chromium.org authored
Move android_webview_build variable to toolchain.gypi to fix arm builders. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/398643006 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22473 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/392033005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22470 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
The android_webview get's it's compiler flags from the Android build system, so we should not be setting these flags in gyp when building the webview. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/399413002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22467 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 17 Jul, 2014 1 commit
-
-
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. Original Review URL: https://codereview.chromium.org/382343003 TBR=jkummerow@chromium.org BUG=384474 LOG=NO Review URL: https://codereview.chromium.org/400573002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22444 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 16 Jul, 2014 2 commits
-
-
rmcilroy@chromium.org authored
This reverts commit r22425 for breaking the Arm debug builder. BUG=384474 TBR=jkummerow@chromium.org Review URL: https://codereview.chromium.org/393273002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22427 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
-
- 09 Jul, 2014 1 commit
-
-
dusan.milosavljevic@rt-rk.com authored
Summary: - Changes in common code are mainly boilerplate changes, gyp and test status files updates. - On mips64 simulator all tests pass from all test units. - Current issues: mjsunit JS debugger tests fail randomly on HW in release mode. Corresponding tests are skipped on HW. - Skipped tests on mips64: test-heap/ReleaseOverReservedPages, mjsunit/debug-* TEST= BUG= R=danno@chromium.org, plind44@gmail.com, ulan@chromium.org Review URL: https://codereview.chromium.org/371923006 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22297 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 03 Jul, 2014 1 commit
-
-
jochen@chromium.org authored
Also remove the "use default platform" compile flag. Instead, the embedder has to provide the platform. Change all binaries to use the default platfrom from libplatform. Unless --job-based-sweeping is passed, nothing uses the platform yet, so nothing will break for embedders (yet). BUG=none R=jkummerow@chromium.org LOG=y Review URL: https://codereview.chromium.org/345903004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22180 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 01 Jul, 2014 4 commits
-
-
yangguo@chromium.org authored
Building d8 with msan requires instrumented libc++. Currently the advised way to do this is from a chromium checkout with d8 as target. R=jarin@chromium.org Review URL: https://codereview.chromium.org/361963003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22124 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jarin@chromium.org authored
Android ninja build still failing. TBR=yangguo@chromium.org Review URL: https://codereview.chromium.org/367633003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22119 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jarin@chromium.org authored
This relands r22098. BUG= R=yangguo@chromium.org Review URL: https://codereview.chromium.org/368433006 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22118 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
Currently works only in combination with i18nsupport=off. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/367623002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22109 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 27 Jun, 2014 1 commit
-
-
svenpanne@chromium.org authored
R=bmeurer@chromium.org, mstarzinger@chromium.org Review URL: https://codereview.chromium.org/352823003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22049 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-