1. 19 Jul, 2011 1 commit
  2. 18 Jul, 2011 2 commits
  3. 13 Jul, 2011 3 commits
  4. 08 Jul, 2011 1 commit
  5. 06 Jul, 2011 1 commit
  6. 05 Jul, 2011 2 commits
  7. 01 Jul, 2011 1 commit
  8. 30 Jun, 2011 1 commit
  9. 29 Jun, 2011 2 commits
  10. 24 Jun, 2011 1 commit
  11. 22 Jun, 2011 1 commit
  12. 09 Jun, 2011 1 commit
  13. 08 Jun, 2011 1 commit
  14. 06 Jun, 2011 1 commit
  15. 31 May, 2011 1 commit
    • rossberg@chromium.org's avatar
      Implement set trap for proxies, and revamp class hierarchy in preparation: · 670f947a
      rossberg@chromium.org authored
      - Introduce a class JSReceiver, that is a common superclass of JSObject and
        JSProxy. Use JSReceiver where appropriate (probably lots of places that we
        still have to migrate, but we will find those later with proxy test suite).
      
      - Move appropriate methods to JSReceiver class (SetProperty,
        GetPropertyAttribute, Get/SetPrototype, Lookup, and so on).
      
      - Introduce new JSFunctionProxy subclass of JSProxy. Currently only a stub.
      
      - Overhaul enum InstanceType:
        * Introduce FIRST/LAST_SPEC_OBJECT_TYPE that ranges over all types that
          represent JS objects, and use that consistently to check language types.
        * Rename FIRST/LAST_JS_OBJECT_TYPE and FIRST/LAST_FUNCTION_CLASS_TYPE
          to FIRST/LAST_[NON]CALLABLE_SPEC_OBJECT_TYPE for clarity.
        * Eliminate the overlap over JS_REGEXP_TYPE.
        * Also replace FIRST_JS_OBJECT with FIRST_JS_RECEIVER, but only use it where
          we exclusively talk about the internal representation type.
        * Insert JS_PROXY and JS_FUNCTION_PROXY in the appropriate places.
      
      - Fix all checks concerning classification, especially for functions, to
        use the CALLABLE_SPEC_OBJECT range (that includes funciton proxies).
      
      - Handle proxies in SetProperty (that was the easiest part :) ).
      
      - A few simple test cases.
      
      R=kmillikin@chromium.org
      
      Review URL: http://codereview.chromium.org/6992072
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8126 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      670f947a
  16. 25 May, 2011 1 commit
  17. 24 May, 2011 3 commits
  18. 23 May, 2011 1 commit
  19. 19 May, 2011 1 commit
  20. 18 May, 2011 1 commit
  21. 16 May, 2011 1 commit
  22. 13 May, 2011 2 commits
  23. 09 May, 2011 1 commit
  24. 06 May, 2011 1 commit
  25. 04 May, 2011 1 commit
  26. 03 May, 2011 2 commits
    • kmillikin@chromium.org's avatar
      Simplify include dependencies. · d0fcbb4e
      kmillikin@chromium.org authored
      Try to make sure that accessors.h, data-flow.h, list-inl.h, and
      scopeinfo.h are included only where needed, but without introducing
      implicit dependencies.
      
      Review URL: http://codereview.chromium.org/6903175
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7756 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      d0fcbb4e
    • sgjesse@chromium.org's avatar
      ARM: Changed the handling of compiletime CPU feature detection · 01707c71
      sgjesse@chromium.org authored
      Always use CpuFeaturesImpliedByCompiler() when selecting CPU features. This checks both for CAN_USE_ARMV7_INSTRUCTIONS and CAN_USE_VFP_INSTRUCTIONS and for GCC preprocessor symbols. This will support using the CAN_USE_XXX for a simulator build used for generating a snapshot followed by a crosscompile using -march= and -mfpu= for selecting the (minimal) target device CPU features. The snapshot will use instructions based on the CAN_USE_XXX whereas the target will at least use features based on both CAN_USE_XXX and -march= and -mfpu=, but will try runtime CPU feature detection a well looking for somethis better.
      
      Remove the compiler based CPU feature detection from the OS::CpuFeaturesImpliedByPlatform() as it did not belong there. Also was already in the CpuFeaturesImpliedByCompiler().
      
      Add the variable 'v8_can_use_vfp_instructions' to the GYP file which can be used to turn on CAN_USE_VFP_INSTRUCTIONS when building V8. I did not add any -mfpu= cflags for this, as there are several options here (e.g. vfp and neon).
      
      R=erik.corry@gmail.com, karlklose@chromium.org
      
      BUG=none
      TEST=none
      
      Review URL: http://codereview.chromium.org//6904164
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7754 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      01707c71
  27. 02 May, 2011 3 commits
  28. 29 Apr, 2011 2 commits