Tags: pybricks/micropython
Tags
py/gc: Ensure gc_alloc calls MICROPY_GC_HOOK_LOOP at least once. If MICROPY_GC_HOOK_LOOP runs an event loop only once in N iterations, it is important that it starts at 0 to ensure that it is called at least once. This fixes the hook loop not being called often enough in certain special cases like: while True: a = "{}".format("h"[0] * 2) Idea by David Lechner <[email protected]> Signed-off-by: Laurens Valk <[email protected]>
py/stackctrl: Add gcc pragmas to ignore dangling-pointer warning. This warning became apparent in gcc 13. Signed-off-by: Damien George <[email protected]>
fixup! ports/unix/modummap: add new ummap module
tests/extmod/ussl_basic: Fix .exp file. Since the test calls close twice, we expect to get the ioctl printed twice. Signed-off-by: David Lechner <[email protected]>
pybricks: Revert "extmod/modussl_mbedtls: Fix support for ioctl(MP_ST… …REAM_POLL)." This reverts commit ed58d6e. This is causing ev3dev tests to fail.
py/gc: MICROPY_GC_HOOK_LOOP improvements. - Add MICROPY_GC_HOOK_LOOP to gc_info() and gc_alloc(). Both of these can be long running (many milliseconds) which is too long to be blocking in some applications. - Pass loop variable to MICROPY_GC_HOOK_LOOP(i) macro so that implementers can use it, e.g. to improve performance by only calling a function every X number of iterations. - Drop outer call to MICROPY_GC_HOOK_LOOP in gc_mark_subtree().
py/gc: MICROPY_GC_HOOK_LOOP improvements. - Add MICROPY_GC_HOOK_LOOP to gc_info() and gc_alloc(). Both of these can be long running (many milliseconds) which is too long to be blocking in some applications. - Pass loop variable to MICROPY_GC_HOOK_LOOP(i) macro so that implementers can use it, e.g. to improve performance by only calling a function every X number of iterations. - Drop outer call to MICROPY_GC_HOOK_LOOP in gc_mark_subtree().
py/obj: Add MP_NOINLINE to mp_obj_malloc_helper. As the comment in py/obj.h says: > Implementing this as a call rather than inline saves 8 bytes per usage. So in order to get this savings, we need to tell the compiler to never inline the function. Signed-off-by: David Lechner <[email protected]>
py/gc: MICROPY_GC_HOOK_LOOP improvements. - Add MICROPY_GC_HOOK_LOOP to gc_info() and gc_alloc(). Both of these can be long running (many milliseconds) which is too long to be blocking in some applications. - Pass loop variable to MICROPY_GC_HOOK_LOOP(i) macro so that implementers can use it, e.g. to improve performance by only calling a function every X number of iterations. - Drop outer call to MICROPY_GC_HOOK_LOOP in gc_mark_subtree().
py/gc: MICROPY_GC_HOOK_LOOP improvements. - Add MICROPY_GC_HOOK_LOOP to gc_info() and gc_alloc(). Both of these can be long running (many milliseconds) which is too long to be blocking in some applications. - Pass loop variable to MICROPY_GC_HOOK_LOOP(i) macro so that implementers can use it, e.g. to improve performance by only calling a function every X number of iterations.
PreviousNext