1. 30 Sep, 2016 2 commits
  2. 18 Dec, 2015 1 commit
    • Damien George's avatar
      py: Add MICROPY_ENABLE_COMPILER and MICROPY_PY_BUILTINS_EVAL_EXEC opts. · dd5353a4
      Damien George authored
      MICROPY_ENABLE_COMPILER can be used to enable/disable the entire compiler,
      which is useful when only loading of pre-compiled bytecode is supported.
      It is enabled by default.
      
      MICROPY_PY_BUILTINS_EVAL_EXEC controls support of eval and exec builtin
      functions.  By default they are only included if MICROPY_ENABLE_COMPILER
      is enabled.
      
      Disabling both options saves about 40k of code size on 32-bit x86.
      dd5353a4
  3. 17 Aug, 2015 1 commit
    • Damien George's avatar
      unix-cpy: Remove unix-cpy. It's no longer needed. · 65dc960e
      Damien George authored
      unix-cpy was originally written to get semantic equivalent with CPython
      without writing functional tests.  When writing the initial
      implementation of uPy it was a long way between lexer and functional
      tests, so the half-way test was to make sure that the bytecode was
      correct.  The idea was that if the uPy bytecode matched CPython 1-1 then
      uPy would be proper Python if the bytecodes acted correctly.  And having
      matching bytecode meant that it was less likely to miss some deep
      subtlety in the Python semantics that would require an architectural
      change later on.
      
      But that is all history and it no longer makes sense to retain the
      ability to output CPython bytecode, because:
      
      1. It outputs CPython 3.3 compatible bytecode.  CPython's bytecode
      changes from version to version, and seems to have changed quite a bit
      in 3.5.  There's no point in changing the bytecode output to match
      CPython anymore.
      
      2. uPy and CPy do different optimisations to the bytecode which makes it
      harder to match.
      
      3. The bytecode tests are not run.  They were never part of Travis and
      are not run locally anymore.
      
      4. The EMIT_CPYTHON option needs a lot of extra source code which adds
      heaps of noise, especially in compile.c.
      
      5. Now that there is an extensive test suite (which tests functionality)
      there is no need to match the bytecode.  Some very subtle behaviour is
      tested with the test suite and passing these tests is a much better
      way to stay Python-language compliant, rather than trying to match
      CPy bytecode.
      65dc960e
  4. 01 Jan, 2015 1 commit
  5. 21 Dec, 2014 1 commit
  6. 08 Sep, 2014 1 commit
  7. 30 Aug, 2014 1 commit
  8. 15 Aug, 2014 1 commit
  9. 21 Jun, 2014 1 commit
  10. 21 May, 2014 1 commit
    • Damien George's avatar
      Tidy up some configuration options. · 58ebde46
      Damien George authored
      MP_ALLOC_* -> MICROPY_ALLOC_*
      MICROPY_PATH_MAX -> MICROPY_ALLOC_PATH_MAX
      MICROPY_ENABLE_REPL_HELPERS -> MICROPY_HELPER_REPL
      MICROPY_ENABLE_LEXER_UNIX -> MICROPY_HELPER_LEXER_UNIX
      MICROPY_EXTRA_* -> MICROPY_PORT_*
      
      See issue #35.
      58ebde46
  11. 05 May, 2014 1 commit
    • Damien George's avatar
      py: Turn down amount of RAM parser and compiler use. · 66e18f04
      Damien George authored
      There are 2 locations in parser, and 1 in compiler, where memory
      allocation is not precise.  In the parser it's the rule stack and result
      stack, in the compiler it's the array for the identifiers in the current
      scope.  All other mallocs are exact (ie they don't allocate more than is
      needed).
      
      This patch adds tuning options (MP_ALLOC_*) to mpconfig.h for these 3
      inexact allocations.
      
      The inexact allocations in the parser should actually be close to
      logarithmic: you need an exponentially larger script (absent pathological
      cases) to use up more room on the rule and result stacks.  As such, the
      default allocation policy for these is now to start with a modest sized
      stack, but grow only in small increments.
      
      For the identifier arrays in the compiler, these now start out quite
      small (4 entries, since most functions don't have that many ids), and
      grow incrementally by 6 (since if you have more ids than 4, you probably
      have quite a few more, but it wouldn't be exponentially more).
      
      Partially addresses issue #560.
      66e18f04
  12. 03 May, 2014 1 commit
    • Damien George's avatar
      Add license header to (almost) all files. · 04b9147e
      Damien George authored
      Blanket wide to all .c and .h files.  Some files originating from ST are
      difficult to deal with (license wise) so it was left out of those.
      
      Also merged modpyb.h, modos.h, modstm.h and modtime.h in stmhal/.
      04b9147e
  13. 27 Apr, 2014 1 commit
  14. 13 Apr, 2014 1 commit
    • Damien George's avatar
      py: Remove unique_codes from emitglue.c. Replace with pointers. · df8127a1
      Damien George authored
      Attempt to address issue #386.  unique_code_id's have been removed and
      replaced with a pointer to the "raw code" information.  This pointer is
      stored in the actual byte code (aligned, so the GC can trace it), so
      that raw code (ie byte code, native code and inline assembler) is kept
      only for as long as it is needed.  In memory it's now like a tree: the
      outer module's byte code points directly to its children's raw code.  So
      when the outer code gets freed, if there are no remaining functions that
      need the raw code, then the children's code gets freed as well.
      
      This is pretty much like CPython does it, except that CPython stores
      indexes in the byte code rather than machine pointers.  These indices
      index the per-function constant table in order to find the relevant
      code.
      df8127a1
  15. 09 Apr, 2014 2 commits
  16. 17 Mar, 2014 1 commit
    • xbe's avatar
      py: Clean up includes. · efe34223
      xbe authored
      Remove unnecessary includes. Add includes that improve portability.
      efe34223
  17. 15 Feb, 2014 1 commit
  18. 24 Jan, 2014 1 commit
  19. 23 Jan, 2014 1 commit
  20. 21 Jan, 2014 1 commit
  21. 19 Jan, 2014 1 commit
  22. 06 Jan, 2014 2 commits
  23. 30 Dec, 2013 1 commit
  24. 29 Dec, 2013 1 commit
  25. 21 Dec, 2013 1 commit
    • Damien's avatar
      Change object representation from 1 big union to individual structs. · d99b0528
      Damien authored
      A big change.  Micro Python objects are allocated as individual structs
      with the first element being a pointer to the type information (which
      is itself an object).  This scheme follows CPython.  Much more flexible,
      not necessarily slower, uses same heap memory, and can allocate objects
      statically.
      
      Also change name prefix, from py_ to mp_ (mp for Micro Python).
      d99b0528
  26. 11 Dec, 2013 1 commit
  27. 20 Oct, 2013 1 commit
  28. 12 Oct, 2013 1 commit
  29. 05 Oct, 2013 3 commits
  30. 04 Oct, 2013 1 commit