- 04 Nov, 2016 1 commit
-
-
Paul Sokolovsky authored
-
- 03 Nov, 2016 7 commits
-
-
Paul Sokolovsky authored
Use normal mp_int_t/mp_uint_t types, algorithms (hm, formulas) can work with any type width.
-
stijn authored
-
stijn authored
-
Damien George authored
Following best-practice use of the const feature, to make it compatible with Python.
-
Damien George authored
All float constants in the core should use this macro to prevent unnecessary creation of double-precision floats, which makes code less efficient.
-
Damien George authored
This helps to test floating point code on Cortex-M hardware. As part of this patch the link-time-optimisation was disabled because it wasn't compatible with software FP support. In particular, the linker could not find the __aeabi_f2d, __aeabi_d2f etc functions even though they were provided by lib/libm/math.c.
-
Damien George authored
This allows it to be used only when the hardware supports VFP instructions, preventing compile errors.
-
- 02 Nov, 2016 4 commits
-
-
Colin Hogben authored
With MICROPY_ENABLE_GC set to false the alternate memory manager may not clear all memory that is allocated, so it must be cleared in m_malloc0.
-
Alex March authored
-
Colin Hogben authored
In both parse.c and qstr.c, an internal chunking allocator tidies up by calling m_renew to shrink an allocated chunk to the size used, and assumes that the chunk will not move. However, when MICROPY_ENABLE_GC is false, m_renew calls the system realloc, which does not guarantee this behaviour. Environments where realloc may return a different pointer include: (1) mbed-os with MBED_HEAP_STATS_ENABLED (which adds a wrapper around malloc & friends; this is where I was hit by the bug); (2) valgrind on linux (how I diagnosed it). The fix is to call m_renew_maybe with allow_move=false.
-
ernitron authored
-
- 01 Nov, 2016 7 commits
-
-
Paul Sokolovsky authored
-
Paul Sokolovsky authored
Size 64 was incorrect and will lead to stack corruption. Size 88 was verified empirically. Also, allow to skip defining it if MD5_CTX preprocessor macro is already defined (to avoid header conflict).
-
Paul Sokolovsky authored
-
Jan Pochyla authored
-
Paul Sokolovsky authored
ESP8266 SDK2.0 fixes (at least, I can't reproduce it) an infamous bug with crash during scan. 36K seams to be a safe value based on a download test (test_dl.py), over 1GB was downloaded. More testing is needed, but let's have other people participate by committing it now.
-
puuu authored
There is no automatic reconnect after wlan.active(False); wlan.active(True). This commit provide the possibility to run wlan.connect() without parameter, to reconnect to the previously connected AP. resolve #2493
-
Paul Sokolovsky authored
-
- 31 Oct, 2016 4 commits
-
-
Paul Sokolovsky authored
-
Paul Sokolovsky authored
It's mandatory function which should be present in every port. Even if it's not, in the stdlib intro we waarn users that a particular port can lack anything of described in the docs.
-
Pavol Rusnak authored
-
Pavol Rusnak authored
-
- 30 Oct, 2016 9 commits
-
-
Paul Sokolovsky authored
-
Paul Sokolovsky authored
-
Paul Sokolovsky authored
Also, drop ::only directive.
-
Paul Sokolovsky authored
-
Paul Sokolovsky authored
-
Paul Sokolovsky authored
-
Fabio Utzig authored
-
Paul Sokolovsky authored
Now the function properly uses ring arithmetic to return signed value in range (inclusive): [-MICROPY_PY_UTIME_TICKS_PERIOD/2, MICROPY_PY_UTIME_TICKS_PERIOD/2-1]. That means that function can properly process 2 time values away from each other within MICROPY_PY_UTIME_TICKS_PERIOD/2 ticks, but away in both directions. For example, if tick value 'a' predates tick value 'b', ticks_diff(a, b) will return negative value, and positive value otherwise. But at positive value of MICROPY_PY_UTIME_TICKS_PERIOD/2-1, the result of the function will wrap around to negative -MICROPY_PY_UTIME_TICKS_PERIOD/2, in other words, if a follows b in more than MICROPY_PY_UTIME_TICKS_PERIOD/2 - 1 ticks, the function will "consider" a to actually predate b.
-
Paul Sokolovsky authored
Using MICROPY_PY_UTIME_TICKS_PERIOD config var.
-
- 29 Oct, 2016 8 commits
-
-
Paul Sokolovsky authored
-
Paul Sokolovsky authored
-
Paul Sokolovsky authored
-
Paul Sokolovsky authored
-
Paul Sokolovsky authored
To fix coverage build.
-
Paul Sokolovsky authored
mp_hal_ticks_ms, mp_hal_ticks_us taken from unix port, mp_hal_ticks_cpu dummy.
-
Paul Sokolovsky authored
-
Paul Sokolovsky authored
Ported from unix port.
-