[v8-dev] Remove semicolons from tools/test.py (issue6822046)

2011-04-11 Thread ricow
Reviewers: Karl Klose, Description: Remove semicolons from tools/test.py Please review this at http://codereview.chromium.org/6822046/ SVN Base: http://v8.googlecode.com/svn/branches/bleeding_edge/ Affected files: M tools/test.py Index: tools/test.py ===

[v8-dev] [v8] r7582 committed - ARM: Add optimization for constant RHS in DoMulI....

2011-04-11 Thread codesite-noreply
Revision: 7582 Author: karlkl...@chromium.org Date: Mon Apr 11 23:44:15 2011 Log: ARM: Add optimization for constant RHS in DoMulI. Patch by ARM Ltd. Review URL: http://codereview.chromium.org/6756033 http://code.google.com/p/v8/source/detail?r=7582 Modified: /branches/bleeding_edge

[v8-dev] [v8] r7581 committed - Fix tools/test.py to allow CTRL+C to work correctly again....

2011-04-11 Thread codesite-noreply
Revision: 7581 Author: ri...@chromium.org Date: Mon Apr 11 23:26:38 2011 Log: Fix tools/test.py to allow CTRL+C to work correctly again. This also changes the AfterRun functions to allow None as the passed in parameter. Review URL: http://codereview.chromium.org/6824040 http://code.

[v8-dev] [v8] r7580 committed - ARM: Always enable ARMv7 when VFPv3 is enabled....

2011-04-11 Thread codesite-noreply
Revision: 7580 Author: sgje...@chromium.org Date: Mon Apr 11 23:12:45 2011 Log: ARM: Always enable ARMv7 when VFPv3 is enabled. R=vego...@chromium.org, rodolph.perfe...@gmail.com BUG=v8:1317 TEST= Review URL: http://codereview.chromium.org//6825037 http://code.google.com/p/v8/source/

[v8-dev] [v8] r7579 committed - Merge r7578 "Fix retained object info leak." to trunk...

2011-04-11 Thread codesite-noreply
Revision: 7579 Author: ri...@chromium.org Date: Mon Apr 11 22:56:07 2011 Log: Merge r7578 "Fix retained object info leak." to trunk Review URL: http://codereview.chromium.org/6813104 http://code.google.com/p/v8/source/detail?r=7579 Modified: /trunk/src/global-handles.h /trunk/src/ver

[v8-dev] Merge r7578 "Fix retained object info leak." to trunk (issue6813104)

2011-04-11 Thread ricow
Reviewers: Kasper Lund, Description: Merge r7578 "Fix retained object info leak." to trunk Please review this at http://codereview.chromium.org/6813104/ SVN Base: http://v8.googlecode.com/svn/trunk/ Affected files: M src/global-handles.h M src/version.cc Index: src/global-handles

[v8-dev] Re: Merge r7578 "Fix retained object info leak." to trunk (issue6813104)

2011-04-11 Thread Kasper Lund
LGTM. On Tue, Apr 12, 2011 at 7:51 AM, wrote: > Reviewers: Kasper Lund, > > Description: > Merge r7578 "Fix retained object info leak." to trunk > > Please review this at http://codereview.chromium.org/6813104/ > > SVN Base: http://v8.googlecode.com/svn/trunk/ > > Affected files: >  M     src/gl

[v8-dev] [v8] r7578 committed - Fix retained object info leak....

2011-04-11 Thread codesite-noreply
Revision: 7578 Author: vita...@chromium.org Date: Mon Apr 11 22:08:13 2011 Log: Fix retained object info leak. Review URL: http://codereview.chromium.org/6813101 http://code.google.com/p/v8/source/detail?r=7578 Modified: /branches/bleeding_edge/src/global-handles.h =

Re: [v8-dev] Fix retained object info leak. (issue6813101)

2011-04-11 Thread Kasper Lund
LGTM, but consider guarding against repeated ObjectGroup::Dispose invocations in debug mode (maybe this also applies to other Dispose methods). Feel free to *not* do this as part of this CL. On Tue, Apr 12, 2011 at 6:51 AM, wrote: > Reviewers: Mads Ager, > > Description: > Fix retained object in

[v8-dev] Fix retained object info leak. (issue6813101)

2011-04-11 Thread vitalyr
Reviewers: Mads Ager, Description: Fix retained object info leak. Please review this at http://codereview.chromium.org/6813101/ Affected files: M src/global-handles.h Index: src/global-handles.h diff --git a/src/global-handles.h b/src/global-handles.h index 3b6b7b3a7e28c783bab14dc2f463bd7

[v8-dev] Re: Another attempt to fix Win build. (issue6825061)

2011-04-11 Thread Dmitry Lomov
Indeed - I'll add that. On Mon, Apr 11, 2011 at 7:40 PM, wrote: > > http://codereview.chromium.org/6825061/diff/1/src/platform-win32.cc > File src/platform-win32.cc (right): > > > http://codereview.chromium.org/6825061/diff/1/src/platform-win32.cc#newcode1531 > src/platform-win32.cc:1531: _begin

[v8-dev] Re: Another attempt to fix Win build. (issue6825061)

2011-04-11 Thread vitalyr
http://codereview.chromium.org/6825061/diff/1/src/platform-win32.cc File src/platform-win32.cc (right): http://codereview.chromium.org/6825061/diff/1/src/platform-win32.cc#newcode1531 src/platform-win32.cc:1531: _beginthreadex(NULL, Shouldn't we still assert thread creation succeeded? http://co

[v8-dev] Fix Win32 build (issue6822042)

2011-04-11 Thread vitalyr
LGTM http://codereview.chromium.org/6822042/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] [v8] r7577 committed - Another attempt to fix Win build....

2011-04-11 Thread codesite-noreply
Revision: 7577 Author: dim...@chromium.org Date: Mon Apr 11 17:49:30 2011 Log: Another attempt to fix Win build. Review URL: http://codereview.chromium.org/6825061 http://code.google.com/p/v8/source/detail?r=7577 Modified: /branches/bleeding_edge/src/platform-win32.cc ===

[v8-dev] Another attempt to fix Win build. (issue6825061)

2011-04-11 Thread dimich
Reviewers: Vitaly Repeshko, Message: TBR=vitalyr Description: Another attempt to fix Win build. Please review this at http://codereview.chromium.org/6825061/ SVN Base: http://v8.googlecode.com/svn/branches/bleeding_edge/ Affected files: M src/platform-win32.cc Index: src/platform-win3

[v8-dev] [v8] r7576 committed - Fix build borkage due to r7575...

2011-04-11 Thread codesite-noreply
Revision: 7576 Author: dim...@chromium.org Date: Mon Apr 11 17:42:27 2011 Log: Fix build borkage due to r7575 (landing for Dmitry Lomov) Review URL: http://codereview.chromium.org/6823065 http://code.google.com/p/v8/source/detail?r=7576 Modified: /branches/bleeding_edge/src/platform-w

[v8-dev] Fix build borkage due to r7575 (issue6823065)

2011-04-11 Thread dimich
Reviewers: Vitaly Repeshko, Message: TBR=vitalyr Original patch: http://codereview.chromium.org/6822042/ Description: Fix build borkage due to r7575 (landing for Dmitry Lomov) Please review this at http://codereview.chromium.org/6823065/ SVN Base: http://v8.googlecode.com/svn/branches/bleeding

[v8-dev] Re: Issue 1244 in v8: v8::internal::Runtime_SetProperty comparison always false due to limited range of data type

2011-04-11 Thread codesite-noreply
Comment #17 on issue 1244 by coldredl...@gmail.com: v8::internal::Runtime_SetProperty comparison always false due to limited range of data type http://code.google.com/p/v8/issues/detail?id=1244 can this fix be merged back into 3.1? -- v8-dev mailing list v8-dev@googlegroups.com http://grou

[v8-dev] Re: Do not rely on uniquiness of pthread_t (issue6816038)

2011-04-11 Thread dslomov
Fix for Win32 build - I need help landing this as I do not have presmissions. http://codereview.chromium.org/6816038/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] [v8] r7575 committed - Do not rely on uniqueness of pthread_t...

2011-04-11 Thread codesite-noreply
Revision: 7575 Author: vita...@chromium.org Date: Mon Apr 11 16:46:22 2011 Log: Do not rely on uniqueness of pthread_t Patch by Dmitry Lomov. pthreads implementations are free to reuse pthread_t (thread id) after the thread has died. This change gets rid of ThreadHandle class and repl

[v8-dev] Re: Add v8Locale.Collator (issue6673011)

2011-04-11 Thread cira
http://codereview.chromium.org/6673011/diff/17002/src/extensions/experimental/collator.cc File src/extensions/experimental/collator.cc (right): http://codereview.chromium.org/6673011/diff/17002/src/extensions/experimental/collator.cc#newcode69 src/extensions/experimental/collator.cc:69: static v

[v8-dev] Re: Add v8Locale.Collator (issue6673011)

2011-04-11 Thread jshin
I left alone the binding part as was done initially. So, directly passing 'collator.compare' wouldn't work because 'compare' is not bound to a Collator. We can sort that out once the ECMAScript committee has an agreement. For internal use in ChromeOS, it should not matter. http://codereview

[v8-dev] Add global setup for runtime profiler. (issue6825054)

2011-04-11 Thread vitalyr
Reviewers: Mads Ager, Description: Add global setup for runtime profiler. Whether it's enabled or not must not change while we're running. Let's not waste time recomputing it. This also makes the VM state tracking code slightly more lightweight. Please review this at http://codereview.chromium.

[v8-dev] Issue 1321 in v8: ToObject should throw when called with null or undefined.

2011-04-11 Thread codesite-noreply
Status: New Owner: New issue 1321 by a...@chromium.org: ToObject should throw when called with null or undefined. http://code.google.com/p/v8/issues/detail?id=1321 The spec has plenty of places where ToObject is being used and it should throw a TypeError if called in undefined or null

[v8-dev] Re: Do not rely on uniquiness of pthread_t (issue6816038)

2011-04-11 Thread vitalyr
Still LGTM http://codereview.chromium.org/6816038/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] Re: Do not rely on uniquiness of pthread_t (issue6816038)

2011-04-11 Thread dslomov
Style issues fixed + use atomic for highest_thread_id_ http://codereview.chromium.org/6816038/diff/5001/src/isolate.cc File src/isolate.cc (right): http://codereview.chromium.org/6816038/diff/5001/src/isolate.cc#newcode57 src/isolate.cc:57: Mutex* ThreadId::thread_id_process_wide_mutex_ = OS::C

[v8-dev] Moving JavaScript code from i18n-extension.cc into i18n.js file using (issue6825049)

2011-04-11 Thread cira
Reviewers: Mads Ager, Message: We have to move JavaScript code from cc file since it's becoming increasingly harder to edit without errors. In case you don't like me adding I18N enum to natives.h, I could change js2c.py to generate different files depending on TYPE (CORE, D8, I18N) and then

[v8-dev] Fit Representation and HType in one word to make HValue smaller. (issue6813091)

2011-04-11 Thread vitalyr
Reviewers: fschneider, Description: Fit Representation and HType in one word to make HValue smaller. Please review this at http://codereview.chromium.org/6813091/ Affected files: M src/hydrogen-instructions.h Index: src/hydrogen-instructions.h diff --git a/src/hydrogen-instructions.h b/src/

[v8-dev] Re: Do not rely on uniquiness of pthread_t (issue6816038)

2011-04-11 Thread dslomov
Thanks for the review - I'll fix the style issues. I have two comments on your comments. http://codereview.chromium.org/6816038/diff/5001/src/isolate.cc File src/isolate.cc (right): http://codereview.chromium.org/6816038/diff/5001/src/isolate.cc#newcode57 src/isolate.cc:57: Mutex* ThreadId::th

[v8-dev] Re: Fix JS ratio computation on startup. (issue6826026)

2011-04-11 Thread vitalyr
http://codereview.chromium.org/6826026/diff/1/src/runtime-profiler.cc File src/runtime-profiler.cc (right): http://codereview.chromium.org/6826026/diff/1/src/runtime-profiler.cc#newcode135 src/runtime-profiler.cc:135: state_counts_[IN_NON_JS_STATE] = kStateWindowSize; On 2011/04/11 06:10:06, Kas

[v8-dev] Re: Allow recursive messages reporting as it is already used. (issue6820003)

2011-04-11 Thread vitalyr
LGTM http://codereview.chromium.org/6820003/diff/6/src/messages.cc File src/messages.cc (right): http://codereview.chromium.org/6820003/diff/6/src/messages.cc#newcode134 src/messages.cc:134: v8::TryCatch tryCatch; nit: noCamelCase http://codereview.chromium.org/6820003/diff/6/test/cctest/test-

[v8-dev] Re: Do not rely on uniquiness of pthread_t (issue6816038)

2011-04-11 Thread vitalyr
LGTM with a few style nits and one real comment. http://codereview.chromium.org/6816038/diff/5001/src/isolate.cc File src/isolate.cc (right): http://codereview.chromium.org/6816038/diff/5001/src/isolate.cc#newcode57 src/isolate.cc:57: Mutex* ThreadId::thread_id_process_wide_mutex_ = OS::CreateM

[v8-dev] Re: Allow recursive messages reporting as it is already used. (issue6820003)

2011-04-11 Thread antonm
thanks a lot for review, guys. Landed. http://codereview.chromium.org/6820003/diff/1/test/cctest/test-api.cc File test/cctest/test-api.cc (left): http://codereview.chromium.org/6820003/diff/1/test/cctest/test-api.cc#oldcode8680 test/cctest/test-api.cc:8680: CompileRun("throw 'ThrowInJS';"); On

[v8-dev] [v8] r7574 committed - Allow recursive messages reporting as it is already used....

2011-04-11 Thread codesite-noreply
Revision: 7574 Author: ant...@chromium.org Date: Mon Apr 11 09:16:52 2011 Log: Allow recursive messages reporting as it is already used. Instead discard unhandled exceptions thown while running message listeners. Review URL: http://codereview.chromium.org/6820003 http://code.google.co

[v8-dev] Issue 1320 in v8: LiveEdit: text differencer fails with out of memory on large files

2011-04-11 Thread codesite-noreply
Status: Accepted Owner: peter.ry...@gmail.com Labels: Type-Bug Priority-Medium New issue 1320 by peter.ry...@gmail.com: LiveEdit: text differencer fails with out of memory on large files http://code.google.com/p/v8/issues/detail?id=1320 If you try to edit file with many lines, text difference

[v8-dev] Change the list of statements that are inlineable into a black-list. (issue6825042)

2011-04-11 Thread fschneider
Reviewers: Kevin Millikin, Kasper Lund, Description: Change the list of statements that are inlineable into a black-list. Before we had a white-list of things that we allow inside inlined functions. This way we can enable new constructs one-by-one. Please review this at http://codereview.chrom

[v8-dev] Re: Fix tools/test.py to allow CTRL+C to work correctly again. (issue6824040)

2011-04-11 Thread lrn
LGTM, to the limit of my Python readability. http://codereview.chromium.org/6824040/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] Re: Allow recursive messages reporting as it is already used. (issue6820003)

2011-04-11 Thread Anton Muhin
Yep. On Mon, Apr 11, 2011 at 3:39 PM, wrote: > OK, LGTM > > This takes it roughly back to what it was for this part, right? > > http://codereview.chromium.org/6820003/ > -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] Re: ARM: Always enable ARMv7 when VFPv3 is enabled. (issue6825037)

2011-04-11 Thread Rodolph Perfetta
I have checked and currently there is no way to tell which vfp version is specified using gcc defines. so LGTM. On 11 April 2011 15:10, wrote: > > http://codereview.chromium.org/6825037/diff/2001/src/arm/assembler-arm.cc > File src/arm/assembler-arm.cc (right): > > > http://codereview.chromium.

[v8-dev] Fix tools/test.py to allow CTRL+C to work correctly again. (issue6824040)

2011-04-11 Thread ricow
Reviewers: Lasse Reichstein, Description: Fix tools/test.py to allow CTRL+C to work correctly again. This also changes the AfterRun functions to allow None as the passed in parameter. Please review this at http://codereview.chromium.org/6824040/ SVN Base: http://v8.googlecode.com/svn/branches/

[v8-dev] Re: ARM: Always enable ARMv7 when VFPv3 is enabled. (issue6825037)

2011-04-11 Thread sgjesse
http://codereview.chromium.org/6825037/diff/2001/src/arm/assembler-arm.cc File src/arm/assembler-arm.cc (right): http://codereview.chromium.org/6825037/diff/2001/src/arm/assembler-arm.cc#newcode63 src/arm/assembler-arm.cc:63: #if defined(__VFP_FP__) && !defined(__SOFTFP__) On 2011/04/11 12:48:55

[v8-dev] [v8] r7573 committed - Bring test262 expectations up-to-date....

2011-04-11 Thread codesite-noreply
Revision: 7573 Author: mm...@chromium.org Date: Mon Apr 11 06:54:30 2011 Log: Bring test262 expectations up-to-date. Add missing *.js files into Xcode project. BUG= TEST= Review URL: http://codereview.chromium.org/6826036 http://code.google.com/p/v8/source/detail?r=7573 Modified: /b

[v8-dev] Re: Bring test262 expectations up-to-date. (issue6826036)

2011-04-11 Thread mmaly
Thanks, landed after making the change. http://codereview.chromium.org/6826036/diff/1/test/test262/harness-adapt.js File test/test262/harness-adapt.js (right): http://codereview.chromium.org/6826036/diff/1/test/test262/harness-adapt.js#newcode55 test/test262/harness-adapt.js:55: res = 'fail'; e

[v8-dev] Re: Introduce runtime function %OptimizeFunctionOnNextCall to manually trigger optimization. (issue6821009)

2011-04-11 Thread jkummerow
...and landed. http://codereview.chromium.org/6821009/diff/1/test/mjsunit/compiler/regress-max.js File test/mjsunit/compiler/regress-max.js (right): http://codereview.chromium.org/6821009/diff/1/test/mjsunit/compiler/regress-max.js#newcode34 test/mjsunit/compiler/regress-max.js:34: %OptimizeFun

[v8-dev] [v8] r7572 committed - Introduce runtime function %OptimizeFunctionOnNextCall to manually tri...

2011-04-11 Thread codesite-noreply
Revision: 7572 Author: jkumme...@chromium.org Date: Mon Apr 11 06:24:50 2011 Log: Introduce runtime function %OptimizeFunctionOnNextCall to manually trigger optimization. TEST=existing unit tests still pass Review URL: http://codereview.chromium.org/6821009 http://code.google.com/p

[v8-dev] Re: Bring test262 expectations up-to-date. (issue6826036)

2011-04-11 Thread ricow
LGTM http://codereview.chromium.org/6826036/diff/1/test/test262/harness-adapt.js File test/test262/harness-adapt.js (right): http://codereview.chromium.org/6826036/diff/1/test/test262/harness-adapt.js#newcode55 test/test262/harness-adapt.js:55: res = 'fail'; error = e; Not from this cl, but put

[v8-dev] Re: Bring test262 expectations up-to-date. (issue6826036)

2011-04-11 Thread ager
LGTM http://codereview.chromium.org/6826036/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] Bring test262 expectations up-to-date. (issue6826036)

2011-04-11 Thread mmaly
Reviewers: Mads Ager, Rico, Description: Bring test262 expectations up-to-date. Add missing *.js files into Xcode project. BUG= TEST= Please review this at http://codereview.chromium.org/6826036/ SVN Base: https://v8.googlecode.com/svn/branches/bleeding_edge Affected files: M test/test262/

[v8-dev] Re: Introduce runtime function %OptimizeFunctionOnNextCall to manually trigger optimization. (issue6821009)

2011-04-11 Thread ager
LGTM http://codereview.chromium.org/6821009/diff/1/test/mjsunit/compiler/regress-max.js File test/mjsunit/compiler/regress-max.js (right): http://codereview.chromium.org/6821009/diff/1/test/mjsunit/compiler/regress-max.js#newcode34 test/mjsunit/compiler/regress-max.js:34: %OptimizeFunctionOnNex

[v8-dev] Re: Introduce runtime function %OptimizeFunctionOnNextCall to manually trigger optimization. (issue6821009)

2011-04-11 Thread jkummerow
I agree with most of your comments, but a few of the methods do not get inlined. Of course I can still remove their optimization triggers if you want me to. http://codereview.chromium.org/6821009/diff/1/test/mjsunit/compiler/optimized-function-calls.js File test/mjsunit/compiler/optimized-func

[v8-dev] Re: ARM: Always enable ARMv7 when VFPv3 is enabled. (issue6825037)

2011-04-11 Thread rodolph . perfetta
http://codereview.chromium.org/6825037/diff/2001/src/arm/assembler-arm.cc File src/arm/assembler-arm.cc (right): http://codereview.chromium.org/6825037/diff/2001/src/arm/assembler-arm.cc#newcode63 src/arm/assembler-arm.cc:63: #if defined(__VFP_FP__) && !defined(__SOFTFP__) This would be true for

[v8-dev] [v8] r7571 committed - Tagging version 3.2.9

2011-04-11 Thread codesite-noreply
Revision: 7571 Author: karlkl...@chromium.org Date: Mon Apr 11 05:36:56 2011 Log: Tagging version 3.2.9 http://code.google.com/p/v8/source/detail?r=7571 Added: /tags/3.2.9 -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] [v8] r7569 committed - Prepare push to trunk. Now working on version 3.2.10....

2011-04-11 Thread codesite-noreply
Revision: 7569 Author: karlkl...@chromium.org Date: Mon Apr 11 05:14:53 2011 Log: Prepare push to trunk. Now working on version 3.2.10. Review URL: http://codereview.chromium.org/6820029 http://code.google.com/p/v8/source/detail?r=7569 Modified: /branches/bleeding_edge/ChangeLog /bra

[v8-dev] Re: Prepare push to trunk. Now working on version 3.2.10. (issue6820029)

2011-04-11 Thread ager
LGTM with that. http://codereview.chromium.org/6820029/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] Re: Prepare push to trunk. Now working on version 3.2.10. (issue6820029)

2011-04-11 Thread ager
Could you put in a line about the sampler thread suspension fix. That one is important. http://codereview.chromium.org/6820029/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] Issue 1319 in v8: Consider reintroducing IntegerModStub code on ARM

2011-04-11 Thread codesite-noreply
Status: Accepted Owner: sgje...@chromium.org CC: fschnei...@chromium.org Labels: Type-FeatureRequest Priority-Low New issue 1319 by fschnei...@chromium.org: Consider reintroducing IntegerModStub code on ARM http://code.google.com/p/v8/issues/detail?id=1319 In the process of removing unused co

[v8-dev] [v8] r7568 committed - Fix x64 build after r7567

2011-04-11 Thread codesite-noreply
Revision: 7568 Author: mikhail.naga...@gmail.com Date: Mon Apr 11 04:49:55 2011 Log: Fix x64 build after r7567 http://code.google.com/p/v8/source/detail?r=7568 Modified: /branches/bleeding_edge/src/x64/lithium-codegen-x64.cc === --- /branches/bleed

[v8-dev] Re: Issue 1304 in v8: [Cleanup] Brush up 'explicit' usage

2011-04-11 Thread codesite-noreply
Updates: Status: Fixed Comment #1 on issue 1304 by mikhail@gmail.com: [Cleanup] Brush up 'explicit' usage http://code.google.com/p/v8/issues/detail?id=1304 There is a bug in cpplint, which prevents it from detecting non-explicit single-arg constructors marked as inline. I fixed

[v8-dev] Prepare push to trunk. Now working on version 3.2.10. (issue6820029)

2011-04-11 Thread karlklose
Reviewers: Mads Ager, Description: Prepare push to trunk. Now working on version 3.2.10. Please review this at http://codereview.chromium.org/6820029/ SVN Base: http://v8.googlecode.com/svn/branches/bleeding_edge/ Affected files: M ChangeLog M src/version.cc Index: ChangeLog

[v8-dev] Re: Issue 1301 in v8: tests fail & dysfunction on armv7a-hardfloat-linux-gnueabi

2011-04-11 Thread codesite-noreply
Updates: Labels: HW-ARM Comment #3 on issue 1301 by sgje...@chromium.org: tests fail & dysfunction on armv7a-hardfloat-linux-gnueabi http://code.google.com/p/v8/issues/detail?id=1301 (No comment was entered for this change.) -- v8-dev mailing list v8-dev@googlegroups.com http://group

[v8-dev] [v8] r7567 committed - Mark single-argument inline constructors as 'explicit'....

2011-04-11 Thread codesite-noreply
Revision: 7567 Author: mikhail.naga...@gmail.com Date: Mon Apr 11 04:38:34 2011 Log: Mark single-argument inline constructors as 'explicit'. There is currently a bug in cpplint.py hiding this problem. R=sgje...@chromium.org BUG=1304 TEST=none Review URL: http://codereview.chromium.or

[v8-dev] Re: Allow recursive messages reporting as it is already used. (issue6820003)

2011-04-11 Thread ager
OK, LGTM This takes it roughly back to what it was for this part, right? http://codereview.chromium.org/6820003/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] Reenable ctrl-c on tools/test by removing intialization of result in Run. (issue6824038)

2011-04-11 Thread ricow
Reviewers: Lasse Reichstein, Description: Reenable ctrl-c on tools/test by removing intialization of result in Run. The initialization of result was introduced in 7452 in addition to enabling the preparser. Please review this at http://codereview.chromium.org/6824038/ SVN Base: http://v8.googl

[v8-dev] Issue 1318 in v8: Exception location incorrect when using ? : within exception constructor argument list

2011-04-11 Thread codesite-noreply
Status: Accepted Owner: mm...@chromium.org Labels: Type-Bug Priority-Medium New issue 1318 by mm...@chromium.org: Exception location incorrect when using ? : within exception constructor argument list http://code.google.com/p/v8/issues/detail?id=1318 function f(a) { throw new SyntaxError(

[v8-dev] Re: Introduce runtime function %OptimizeFunctionOnNextCall to manually trigger optimization. (issue6821009)

2011-04-11 Thread ager
Looks great. One suggestion for replacing the contents of a test. A number of explicit optimizations of something that should be inlined. I think they can be removed. http://codereview.chromium.org/6821009/diff/1/test/mjsunit/compiler/optimized-function-calls.js File test/mjsunit/compiler/o

[v8-dev] Re: Mark single-argument inline constructors as 'explicit'. (issue6820028)

2011-04-11 Thread sgjesse
LGTM - how about the bug in cpplint.py? http://codereview.chromium.org/6820028/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] Re: ARM: Always enable ARMv7 when VFPv3 is enabled. (issue6825037)

2011-04-11 Thread vegorov
LGTM http://codereview.chromium.org/6825037/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] ARM: Always enable ARMv7 when VFPv3 is enabled. (issue6825037)

2011-04-11 Thread sgjesse
Reviewers: Vyacheslav Egorov, Rodolph Perfetta, Description: ARM: Always enable ARMv7 when VFPv3 is enabled. R=vego...@chromium.org, rodolph.perfe...@gmail.com BUG=v8:1317 TEST= Please review this at http://codereview.chromium.org/6825037/ SVN Base: https://v8.googlecode.com/svn/branches/ble

[v8-dev] Mark single-argument inline constructors as 'explicit'. (issue6820028)

2011-04-11 Thread mnaganov
Reviewers: Søren Gjesse, Description: Mark single-argument inline constructors as 'explicit'. There is currently a bug in cpplint.py hiding this problem. R=sgje...@chromium.org BUG=1304 TEST=none Please review this at http://codereview.chromium.org/6820028/ SVN Base: https://v8.googlecode.co

[v8-dev] Re: Issue 1316 in v8: Builtin ARM disassembler does not support coprocessor instructions

2011-04-11 Thread codesite-noreply
Updates: Status: Fixed Comment #3 on issue 1316 by sgje...@chromium.org: Builtin ARM disassembler does not support coprocessor instructions http://code.google.com/p/v8/issues/detail?id=1316 With r7565 the support for ABI prior to EABI was removed. Together with that the instructions

[v8-dev] Re: Remove code from the deprecated GenericBinaryOpStub. (issue6826032)

2011-04-11 Thread sgjesse
LGTM http://codereview.chromium.org/6826032/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] Remove code from the deprecated GenericBinaryOpStub. (issue6826032)

2011-04-11 Thread fschneider
Reviewers: Søren Gjesse, Description: Remove code from the deprecated GenericBinaryOpStub. All platforms are now using the TypeRecordingBinaryOpStub. I also removed the ARM IntegerModStub which was called from the GenericBinaryOpStub. Please review this at http://codereview.chromium.org/682603

[v8-dev] [v8] r7564 committed - ARM: Fix wrong fall through handling...

2011-04-11 Thread codesite-noreply
Revision: 7564 Author: sgje...@chromium.org Date: Mon Apr 11 01:59:29 2011 Log: ARM: Fix wrong fall through handling Looks like a copy/paste mistake. R=kmilli...@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org//6826031 http://code.google.com/p/v8/source/detail?r=7

[v8-dev] [v8] r7565 committed - ARM: Remove support for ABI prior to EABI...

2011-04-11 Thread codesite-noreply
Revision: 7565 Author: sgje...@chromium.org Date: Mon Apr 11 02:04:30 2011 Log: ARM: Remove support for ABI prior to EABI The support for the old ABI is known to be broken and has been deprecated for some time now. Removed the instructions for loading and storing co-processor regis

[v8-dev] Re: ARM: Remove support for ABI prior to EABI (issue6822025)

2011-04-11 Thread sgjesse
http://codereview.chromium.org/6822025/diff/14/src/arm/code-stubs-arm.cc File src/arm/code-stubs-arm.cc (right): http://codereview.chromium.org/6822025/diff/14/src/arm/code-stubs-arm.cc#newcode951 src/arm/code-stubs-arm.cc:951: // registers 0 and 1. On 2011/04/11 08:48:02, Karl Klose wrote: r0

[v8-dev] Re: ARM: Fix wrong fall through handling (issue6826031)

2011-04-11 Thread kmillikin
LGTM. http://codereview.chromium.org/6826031/ -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev

[v8-dev] ARM: Fix wrong fall through handling (issue6826031)

2011-04-11 Thread sgjesse
Reviewers: Kevin Millikin, Description: ARM: Fix wrong fall through handling Looks like a copy/paste mistake. R=kmilli...@chromium.org BUG= TEST= Please review this at http://codereview.chromium.org/6826031/ SVN Base: https://v8.googlecode.com/svn/branches/bleeding_edge Affected files: M

[v8-dev] Re: ARM: Remove support for ABI prior to EABI (issue6822025)

2011-04-11 Thread karlklose
LGTM. http://codereview.chromium.org/6822025/diff/14/src/arm/code-stubs-arm.cc File src/arm/code-stubs-arm.cc (right): http://codereview.chromium.org/6822025/diff/14/src/arm/code-stubs-arm.cc#newcode951 src/arm/code-stubs-arm.cc:951: // registers 0 and 1. r0 and r1 instead of registers 0 and 1?

[v8-dev] ARM: Remove support for ABI prior to EABI (issue6822025)

2011-04-11 Thread sgjesse
Reviewers: Karl Klose, Description: ARM: Remove support for ABI prior to EABI The support for the old ABI is known to be broken and has been deprecated for some time now. Removed the instructions for loading and storing co-processor registers as they where only used to support the old ABI. R

[v8-dev] Re: Allow recursive messages reporting as it is already used. (issue6820003)

2011-04-11 Thread yurys
http://codereview.chromium.org/6820003/diff/1/test/cctest/test-api.cc File test/cctest/test-api.cc (left): http://codereview.chromium.org/6820003/diff/1/test/cctest/test-api.cc#oldcode8680 test/cctest/test-api.cc:8680: CompileRun("throw 'ThrowInJS';"); Can we rewrite this listener to make it ree