1. 19 Aug, 2015 1 commit
  2. 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.
  3. 26 Jul, 2015 2 commits
  4. 20 Jul, 2015 1 commit
    • Damien George's avatar
      py: Make qstr hash size configurable, defaults to 2 bytes. · c3bd9415
      Damien George authored
      This patch makes configurable, via MICROPY_QSTR_BYTES_IN_HASH, the
      number of bytes used for a qstr hash.  It was originally fixed at 2
      bytes, and now defaults to 2 bytes.  Setting it to 1 byte will save
      ROM and RAM at a small expense of hash collisions.
  5. 14 Jul, 2015 1 commit
    • Damien George's avatar
      py: Improve allocation policy of qstr data. · ade9a052
      Damien George authored
      Previous to this patch all interned strings lived in their own malloc'd
      chunk.  On average this wastes N/2 bytes per interned string, where N is
      the number-of-bytes for a quanta of the memory allocator (16 bytes on 32
      bit archs).
      With this patch interned strings are concatenated into the same malloc'd
      chunk when possible.  Such chunks are enlarged inplace when possible,
      and shrunk to fit when a new chunk is needed.
      RAM savings with this patch are highly varied, but should always show an
      improvement (unless only 3 or 4 strings are interned).  New version
      typically uses about 70% of previous memory for the qstr data, and can
      lead to savings of around 10% of total memory footprint of a running
      Costs about 120 bytes code size on Thumb2 archs (depends on how many
      calls to gc_realloc are made).
  6. 02 Jul, 2015 1 commit
  7. 20 Jun, 2015 1 commit
    • Damien George's avatar
      py: Use a wrapper to explicitly check self argument of builtin methods. · 06593fb0
      Damien George authored
      Previous to this patch a call such as list.append(1, 2) would lead to a
      seg fault.  This is because list.append is a builtin method and the first
      argument to such methods is always assumed to have the correct type.
      Now, when a builtin method is extracted like this it is wrapped in a
      checker object which checks the the type of the first argument before
      calling the builtin function.
      This feature is contrelled by MICROPY_BUILTIN_METHOD_CHECK_SELF_ARG and
      is enabled by default.
      See issue #1216.
  8. 30 May, 2015 1 commit
  9. 24 May, 2015 1 commit
  10. 04 May, 2015 2 commits
  11. 25 Apr, 2015 1 commit
  12. 21 Apr, 2015 1 commit
  13. 19 Apr, 2015 1 commit
  14. 16 Apr, 2015 1 commit
    • Damien George's avatar
      py: Overhaul and simplify printf/pfenv mechanism. · 7f9d1d6a
      Damien George authored
      Previous to this patch the printing mechanism was a bit of a tangled
      mess.  This patch attempts to consolidate printing into one interface.
      All (non-debug) printing now uses the mp_print* family of functions,
      mainly mp_printf.  All these functions take an mp_print_t structure as
      their first argument, and this structure defines the printing backend
      through the "print_strn" function of said structure.
      Printing from the uPy core can reach the platform-defined print code via
      two paths: either through mp_sys_stdout_obj (defined pert port) in
      conjunction with mp_stream_write; or through the mp_plat_print structure
      which uses the MP_PLAT_PRINT_STRN macro to define how string are printed
      on the platform.  The former is only used when MICROPY_PY_IO is defined.
      With this new scheme printing is generally more efficient (less layers
      to go through, less arguments to pass), and, given an mp_print_t*
      structure, one can call mp_print_str for efficiency instead of
      mp_printf("%s", ...).  Code size is also reduced by around 200 bytes on
      Thumb2 archs.
  15. 09 Apr, 2015 1 commit
  16. 06 Apr, 2015 2 commits
  17. 03 Apr, 2015 2 commits
  18. 02 Apr, 2015 2 commits
  19. 26 Mar, 2015 1 commit
  20. 20 Mar, 2015 2 commits
    • stijn's avatar
      py: Allow retrieving a function's __name__. · 3cc17c69
      stijn authored
      Disabled by default.  Enabled on unix and stmhal ports.
    • Paul Sokolovsky's avatar
      py: Implement core of OrderedDict type. · 0ef01d0a
      Paul Sokolovsky authored
      Given that there's already support for "fixed table" maps, which are
      essentially ordered maps, the implementation of OrderedDict just extends
      "fixed table" maps by adding an "is ordered" flag and add/remove
      operations, and reuses 95% of objdict code, just making methods tolerant
      to both dict and OrderedDict.
      Some things are missing so far, like CPython-compatible repr and comparison.
      OrderedDict is Disabled by default; enabled on unix and stmhal ports.
  21. 14 Mar, 2015 1 commit
  22. 11 Mar, 2015 1 commit
  23. 03 Mar, 2015 1 commit
  24. 27 Feb, 2015 1 commit
    • Paul Sokolovsky's avatar
      objarray: Implement array slice assignment. · cefcbb22
      Paul Sokolovsky authored
      This is rarely used feature which takes enough code to implement, so is
      controlled by MICROPY_PY_ARRAY_SLICE_ASSIGN config setting, default off.
      But otherwise it may be useful, as allows to update arbitrary-sized data
      buffers in-place.
      Slice is yet to implement, and actually, slice assignment implemented in
      such a way that RHS of assignment should be array of the exact same item
      typecode as LHS. CPython has it more relaxed, where RHS can be any sequence
      of compatible types (e.g. it's possible to assign list of int's to a
      bytearray slice).
      Overall, when all "slice write" features are implemented, it may cost ~1KB
      of code.
  25. 23 Feb, 2015 1 commit
  26. 22 Feb, 2015 1 commit
  27. 08 Feb, 2015 1 commit
  28. 30 Jan, 2015 1 commit
  29. 20 Jan, 2015 1 commit
  30. 15 Jan, 2015 1 commit
    • Paul Sokolovsky's avatar
      pyexec: Add event-driven variant pyexec_friendly_repl(). · 87bc8e2b
      Paul Sokolovsky authored
      pyexec_friendly_repl_process_char() and friends, useful for ports which
      integrate into existing cooperative multitasking system.
      Unlike readline() refactor before, this was implemented in less formal,
      trial&error process, minor functionality regressions are still known
      (like soft&hard reset support). So, original loop-based pyexec_friendly_repl()
      is left intact, specific implementation selectable by config setting.
  31. 14 Jan, 2015 1 commit
  32. 11 Jan, 2015 1 commit
    • Damien George's avatar
      py: Add MICROPY_QSTR_BYTES_IN_LEN config option, defaulting to 1. · 95836f84
      Damien George authored
      This new config option sets how many fixed-number-of-bytes to use to
      store the length of each qstr.  Previously this was hard coded to 2,
      but, as per issue #1056, this is considered overkill since no-one
      needs identifiers longer than 255 bytes.
      With this patch the number of bytes for the length is configurable, and
      defaults to 1 byte.  The configuration option filters through to the
      makeqstrdata.py script.
      Code size savings going from 2 to 1 byte:
      - unix x64 down by 592 bytes
      - stmhal down by 1148 bytes
      - bare-arm down by 284 bytes
      Also has RAM savings, and will be slightly more efficient in execution.
  33. 10 Jan, 2015 1 commit
  34. 09 Jan, 2015 1 commit