- 09 Oct, 2014 1 commit
-
-
dusan.milosavljevic@imgtec.com authored
TEST= BUG= R=jkummerow@chromium.org, paul.lind@imgtec.com Review URL: https://codereview.chromium.org/618193005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24486 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 08 Oct, 2014 1 commit
-
-
jochen@chromium.org authored
WPO was only enabled to work around an issue with the Isolate's static initializer which no longer exists. Requiring XP on Win64 doesn't make sense. BUG=421363 R=machenbach@chromium.org LOG=y Review URL: https://codereview.chromium.org/637303002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24457 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 01 Oct, 2014 1 commit
-
-
jochen@chromium.org authored
BUG=none R=svenpanne@chromium.org LOG=n git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24354 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 25 Sep, 2014 1 commit
-
-
ulan@chromium.org authored
R=benm@chromium.org, ulan@chromium.org, torne@chromium.org TEST=manual BUG= Review URL: https://codereview.chromium.org/598723002 Patch from Dehao Chen <dehao@google.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24219 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 25 Aug, 2014 1 commit
-
-
yangguo@chromium.org authored
This is to add support for a Link-Time Optimizations experiment in Android Chromium. As it is disabled by default, it won't change anything for most configurations. R=ulan@chromium.org Review URL: https://codereview.chromium.org/497713002 Patch from Fabrice de Gans <fdegans@chromium.org>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23336 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 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 4 commits
-
-
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
-
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
-
- 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
-
- 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
-
- 24 Jun, 2014 1 commit
-
-
haitao.feng@intel.com authored
R=verwaest@chromium.org Review URL: https://codereview.chromium.org/18014003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21955 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 23 Jun, 2014 1 commit
-
-
rmcilroy@chromium.org authored
Simplify the compile time feature detection on Arm: - Define CAN_USE_XXX definitions unconditionally for all target/host toolchain combinations - Rename arm_test / ARM_TEST to arm_test_noprob / ARM_TEST_NO_FEATURE_PROBE - Don't set ARM_TEST_NO_FEATURE_PROBE implicitly on the simulator to make make simulator / native more consistent - Unify CpuFeatures::PrintTarget for simulator and native builds - Remove unecessary CAN_USE_VFP_INSTRUCTIONS definition for android (this is the default for arm_fpu=default) - Add a CpuFeatures::Probe() before calling CpuFeatures::PrintFeatures() in PrintHelp to ensure we have probed features before printing them. BUG=384474 LOG=N R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/340373002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21935 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 02 Jun, 2014 1 commit
-
-
weiliang.lin@intel.com authored
BUG= R=danno@chromium.org Review URL: https://codereview.chromium.org/305643005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21603 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 23 May, 2014 1 commit
-
-
danno@chromium.org authored
Support x87-only platform (ia32 without SSE) R=danno@chromium.org Review URL: https://codereview.chromium.org/293743005 Patch from Weiliang Lin <weiliang.lin@intel.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21469 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 12 May, 2014 1 commit
-
-
m.m.capewell@googlemail.com authored
R=bmeurer@chromium.org, ulan@chromium.org BUG= Review URL: https://codereview.chromium.org/264593002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21258 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 15 Apr, 2014 1 commit
-
-
plind44@gmail.com authored
Important notices: - The snapshot cannot be created for big-endian target in cross-compilation environment on little-endian host using simulator. - In order to have i18n support working on big-endian target, the icudt46b.dat and icudt46b_dat.S files should be generated and upstreamed to ICU repo. - The mjsunit 'nans' test is endian dependent, it is skipped for mips target. - The zlib and Mandreel from Octane 2.0 benchmark are endian dependent due to use of typed arrays. TEST= BUG= R=jkummerow@chromium.org, plind44@gmail.com Review URL: https://codereview.chromium.org/228943009 Patch from Dusan Milosavljevic <Dusan.Milosavljevic@rt-rk.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20778 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Apr, 2014 1 commit
-
-
jochen@chromium.org authored
The problem is that conditions are evaluated before configuration inheritance is resolved, so we can't just define a configuration like this: 'Optdebug': { 'inherits_from': ['Debug'], 'variables': { 'v8_optimized_debug': 2, } } Instead, we have to put the different settings depending on the optimization level into separate configurations, and use conditions inside the concrete configurations to inherit from the correct base class. Common settings go in the base configuration DebugBaseCommon, and v8_optimized_debug dependent settings go into DebugBase{0,1,2} The new Debug configuration inherits from DebugBaseCommon and DebugBase<(v8_optimized_debug), while the new configuration Optdebug inherits from DebugBaseCommon and DebugBase2. BUG=v8:3252 R=machenbach@chromium.org, jkummerow@chromium.org LOG=n Review URL: https://codereview.chromium.org/224443003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20605 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 01 Apr, 2014 1 commit
-
-
jkummerow@chromium.org authored
Bonus cleanup: remove a few duplicate compiler flags R=jarin@chromium.org Review URL: https://codereview.chromium.org/220883003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20402 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 26 Mar, 2014 1 commit
-
-
rmcilroy@chromium.org authored
The -m64 flag isn't supported on Android. Add a similar gyp condition to avoid setting the flag on Android in a similar manner to how the -m32 flag is avoided on android. BUG=354405 LOG=N R=ulan@chromium.org Review URL: https://codereview.chromium.org/212863007 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20289 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 21 Mar, 2014 2 commits
-
-
jochen@chromium.org authored
BUG=354405 R=ulan@chromium.org, rodolph.perfetta@arm.com LOG=y Review URL: https://codereview.chromium.org/207823003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20148 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
BUG=354405 R=machenbach@chromium.org LOG=n Review URL: https://codereview.chromium.org/207793002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20147 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 12 Feb, 2014 1 commit
-
-
ulan@chromium.org authored
BUG=v8:3113 LOG=Y R=jochen@chromium.org, rmcilroy@chromium.org, rodolph.perfetta@arm.com Review URL: https://codereview.chromium.org/148293020 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@19311 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 17 Jan, 2014 1 commit
-
-
jochen@chromium.org authored
BUG=v8:1775 R=machenbach@chromium.org LOG=y Review URL: https://codereview.chromium.org/138273016 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@18656 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 02 Jan, 2014 1 commit
-
-
bmeurer@chromium.org authored
This patch contains contributions from the following members of the BlackBerry Web Technologies team: Eli Fidler <efidler@blackberry.com> Konrad Piascik <kpiascik@blackberry.com> Jeff Rogers <jrogers@blackberry.com> Cosmin Truta <ctruta@blackberry.com> Peter Wang <peter.wang@torchmobile.com.cn> Xiaobo Wang <xiaobwang@blackberry.com> Ming Xie <mxie@blackberry.com> Leo Yang <leoyang@blackberry.com> R=bmeurer@chromium.org, jkummerow@chromium.org Review URL: https://codereview.chromium.org/61153009 Patch from Cosmin Truta <ctruta@blackberry.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@18430 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 11 Dec, 2013 1 commit
-
-
jkummerow@chromium.org authored
BUG=chromium:234135 LOG=Y R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/98543008 Patch from Mostyn Bramley-Moore <mostynb@opera.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@18297 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 18 Nov, 2013 1 commit
-
-
jkummerow@chromium.org authored
I sometimes observe broken pipe errors when I run gyp, which causes the gyp process to fail. This seems to happen if gyp is executed under heavy I/O pressure. This change removes the pipes by replacing "echo |" with "< /dev/null". Technically these are not the same, because "echo |" prints a newline while "< /dev/null" doesn't, but this difference is not significant in the context of the commands in toolchain.gypi. BUG= R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/73623002 Patch from Yuta Kitamura <yutak@chromium.org>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17836 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 25 Oct, 2013 1 commit
-
-
danno@chromium.org authored
Thereby ensuring there is only a minimal performance regression vs. NDEBUG (now it's only about 10% slower rather than ~2x). R=jkummerow@chromium.org, mstarzinger@chromium.org Review URL: https://codereview.chromium.org/39183004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17392 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 14 Oct, 2013 1 commit
-
-
jkummerow@chromium.org authored
This is so that Chromium can have its own overridable default value without colliding with ours. R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/26317009 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17193 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 20 Aug, 2013 1 commit
-
-
jkummerow@chromium.org authored
Also cleans up some uninitialized data I saw while investigating the problem. R=jkummerow@chromium.org, machenbach@chromium.org Review URL: https://codereview.chromium.org/23119004 Patch from Ken Mixter <kmixter@google.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16235 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-