507 Commits

Author	SHA1	Message	Date
Damien George	367178fce7	all: Bump version to 1.29.0-preview. ... Signed-off-by: Damien George <damien@micropython.org>	2026-04-07 13:07:26 +10:00
Damien George	e0e9fbb17e	all: Bump version to 1.28.0. ... Signed-off-by: Damien George <damien@micropython.org>	2026-04-06 23:12:49 +10:00
Damien George	74e945752b	py/modweakref: Implement weakref module with ref and finalize classes. ... This adds support for the standard `weakref` module, to make weak references to Python objects and have callbacks for when an object is reclaimed by the GC. This feature was requested by PyScript, to allow control over the lifetime of external proxy objects (distinct from JS<->Python proxies). Addresses issue #646 (that's nearly a 12 year old issue!). Functionality added here: - `weakref.ref(object [, callback])` create a simple weak reference with optional callback to be called when the object is reclaimed by the GC - `weakref.finalize(object, callback, /, *args, **kwargs)` create a finalize object that holds a weak reference to an object and allows more convenient callback usage and state change The new module is enabled at the "everything" level. The implementation aims to be as efficient as possible, by adding another bit-per-block to the garbage collector, the WTB (weak table). Similar to the finalizer bit (FTB), if a GC block has its corresponding WTB bit set then a weak reference to that block is held. The details of that weak reference are stored in a global map, `mp_weakref_map`, which maps weak reference to ref/finalize objects, allowing the callbacks to be efficiently found when the object is reclaimed. With this feature enabled the overhead is: - 1/128th of the available memory is used for the new WTB table (eg a 128k heap now needs an extra 1k for the WTB). - Code size is increased. - At garbage collection time, there is a small overhead to check if the collected objects had weak references. This check is the same as the existing FTB finaliser scan, so shouldn't add much overhead. If there are weak reference objects alive (ref/finalize objects) then additional time is taken to call the callbacks and do some accounting to clean up the used weak reference. Signed-off-by: Damien George <damien@micropython.org>	2026-03-22 23:02:38 +11:00
Damien George	d4751a164e	py: Add support for PEP 750's t-strings. ... This commit adds support for t-strings by leveraging the existing f-string parser in the lexer. It includes: - t-string parsing in `py/lexer.c` - new built-in `__template__()` function to construct t-string objects - new built-in `Template` and `Interpolation` classes which implement all the functionality from PEP 750 - new built-in `string` module with `templatelib` sub-module, which contains the classes `Template` and `Interpolation` The way the t-string parser works is that an input t-string like: t"hello {name:5}" is converted character-by-character by the lexer/tokenizer to: __template__(("hello ", "",), name, "name", None, "5") For reference, if it were an f-string it would be converted to: "hello {:5}".format(name) Some properties of this implementation: - it's enabled by default at the full feature level, MICROPY_CONFIG_ROM_LEVEL_AT_LEAST_FULL_FEATURES - when enabled on a Cortex-M bare-metal port it costs about +3000 bytes - there are no limits on the size or complexity of t-strings, and it allows arbitrary levels of nesting of f-strings and t-strings (up to the memory available to the compiler) - the 'a' (ascii) conversion specifier is not supported (MicroPython does not have the built-in `ascii` function) - space after conversion specifier, eg t"{x!r :10}", is not supported - arguments to `__template__` and `Interpolation` are not fully validated (it's not necessary, it won't crash if the wrong arguments are passed in) Otherwise the implementation here matches CPython. Signed-off-by: Damien George <damien@micropython.org>	2026-03-09 23:47:33 +11:00
Daniël van de Giessen	71866edc13	py/stream: Use detailed error strings for TLS sockets. ... Both mbedTLS and axTLS have support for producing more detailed error strings. However, these are not used if the error is raised in stream protocol functions (read/write/ioctl). This commit adds support for more detailed error messages from streams. Under the hood it's using a new MP_STREAM_RAISE_ERROR ioctl request to pass the error code back to the stream implementation which can raise a more detailed error. If the ioctl is not implemented, we fall back to the old behaviour and raise an OSError with the error code. Currently the detailed messages are only implemented for TLS sockets since those already had helper functions for raising detailed exceptions, but can be easily implemented in any other stream. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2026-02-07 16:34:20 +11:00
Damien George	03f50d39da	py/mpconfig: Enable MICROPY_PY_FUNCTION_ATTRS_CODE when marshal enabled. ... In case `MICROPY_PY_MARSHAL` is enabled manually. Otherwise the marshal module is not very usable. Signed-off-by: Damien George <damien@micropython.org>	2026-01-27 01:20:36 +11:00
Alessandro Gatti	3980a0c01f	py/misc: Add byte-swapping macros. ... This commit adds byte-swapping macros for 16-, 32-, and 64-bit values. Modern compilers are usually able to detect manual byte/endian swaps and will generate optimised code sequences if they know how to do that. However, in certain situations it may be helpful to let the compiler generate an optimised sequence if it doesn't recognise the pattern. Most compilers provide built-in byte swap operations for 16, 32, and 64 bit values, accessed via "__builtin_bswap<size>", but if those are not available a fallback implementation is provided. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 12:13:34 +11:00
Alessandro Gatti	b0f3ecd96c	py/persistentcode: Decouple native code loading from emitters' presence. ... This commit lets the interpreter load MPY files containing native code even if the target platform does not have a native emitter, or if native code generation is disabled. Native code loading has been tied to native code generation being enabled as a discriminant to allow said operation. This blocks native code loading on platforms that could benefit from such a thing but they don't (and probably won't) have a native code generation target written for them (ie. AArch64 and RISC-V 64). This also forces a firmware image to have a full native code compiler present even if it doesn't need to generate anything, as native modules already have all the code they will ever need to load. There is a new configuration setting, MICROPY_PERSISTENT_CODE_LOAD_NATIVE, that if enabled it will allow loading native code modules even if code generation (MICROPY_EMIT_<platform> and MICROPY_EMIT_INLINE_<platform>) is explicitly turned off. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-26 10:00:02 +01:00
Alessandro Gatti	1df86516e0	py/asmrv32: Reserve a flag for the Zcmp RV32 CPU extension. ... This commit performs the necessary changes to handle an additional RV32 CPU extension flag, for the Zcmp extension in this case. The changes are not limited to RV32-only code, as other parts of the tooling need to be modified for this: the testing framework has to be made aware that an extra bit can be set in sys.implementation._mpy and needs to know how it is called, and "mpy-cross" must be able to actually set that flag bit in the first place via the appropriate command line argument. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-19 17:06:53 +11:00
Damien George	099cc9f507	all: Bump version to 1.28.0-preview. ... Signed-off-by: Damien George <damien@micropython.org>	2025-12-15 10:15:42 +11:00
Damien George	78ff170de9	all: Bump version to 1.27.0. ... Signed-off-by: Damien George <damien@micropython.org>	2025-12-10 01:44:16 +11:00
John Smith	1e5da2642c	shared/runtime: Set exit code according to the SystemExit exception. ... Add abort setup code `nlr_set_abort` to the standard runtime executor. This makes the standard runtime respond to abort signal without any further modifications. - When aborted, the program exits with 137 exit code (configurable, same as posix sig abort), to differentiate from a normal shutdown. - When exited by exception/crash, the program will exit with exit code 1 (configurable). - When exited by exception KeyboardInterrupt, the program will exit with exit code 130 (configurable, same as posix sig int). - When exited with a exit code (from Python environment), this code is propagated. When a different object is passed, exit code is set to 1 and the value printed, to be consistent with Python docs: https://python.readthedocs.io/en/latest/library/exceptions.html#SystemExit Signed-off-by: John Smith <jsmith@jsmith.cz>	2025-11-04 16:47:19 +11:00
Jeff Epler	007f127a61	all: Simplify mp_int_t/mp_uint_t definition. ... Assuming proper C99 language support, we can select "the int type as big as a pointer" (most of the time) or "the 64-bit int type" (nanboxing with REPR_D), and then define everything else automatically. This simplifies port configuration files. And the types can still be overridden if needed. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-23 15:12:28 +11:00
Angus Gratton	3ec8b9a77c	all: Replace legacy name with MicroPython and MPy as applicable. ... With the aim of getting consistency, and removing the need to learn an additional term, replace uses of uPy/uPython with MPy/MicroPython. Rule of thumb was to use "MPy" abbreviation where "CPy" is used nearby, but the full word MicroPython otherwise. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-10-04 00:19:40 +10:00
Jeff Epler	ab00806025	py/mpconfig: Introduce SIZE_FMT macro. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-03 00:45:31 +10:00
Damien George	dcbda765d1	py/modmath: Make MICROPY_PY_MATH_POW_FIX_NAN also fix pow(x, NaN) cases. ... This is needed by the zephyr port. Combining it with the existing `MICROPY_PY_MATH_POW_FIX_NAN` option should be safe, and eliminates the need for a separate option. Signed-off-by: Damien George <damien@micropython.org>	2025-10-01 23:59:15 +10:00
Jeff Epler	a809132921	py: Add MICROPY_USE_GCC_MUL_OVERFLOW_INTRINSIC. ... Most MCUs apart from Cortex-M0 with Thumb 1 have an instruction for computing the "high part" of a multiplication (e.g., the upper 32 bits of a 32x32 multiply). When they do, gcc uses this to implement a small and fast overflow check using the __builtin_mul_overflow intrinsic, which is preferable to the guard division method previously used in smallint.c. However, in contrast to the previous mp_small_int_mul_overflow routine, which checks that the result fits not only within mp_int_t but is SMALL_INT_FITS(), __builtin_mul_overflow only checks for overflow of the C type. As a result, a slight change in the code flow is needed for MP_BINARY_OP_MULTIPLY. Other sites using mp_small_int_mul_overflow already had the result value flow through to a SMALL_INT_FITS check so they didn't need any additional changes. Do similarly for the _ll and _ull multiply overflows checks. Signed-off-by: Jeff Epler <jepler@gmail.com>	2025-10-01 09:23:05 +10:00
Chris Webb	81985d20c9	shared/runtime/mpirq: Check separate hard IRQ stack correctly. ... On the zephyr port, hard IRQ handlers run with a separate stack on a different thread, so each call to mp_irq_dispatch() and mp_irq_handler() has to be wrapped with adjustments to the stack-limit checker. Move these adjustments into the shared mp_irq_dispatch(), introducing MICROPY_STACK_SIZE_HARD_IRQ which a port can define to non-zero if it uses a separate stack for hard IRQ handlers. We only need wrap the hard dispatch case. This should reduce binary size on zephyr without affecting other ports. Signed-off-by: Chris Webb <chris@arachsys.com>	2025-09-25 23:59:24 +10:00
Alessandro Gatti	cb7ca6f1bc	py/asmrv32: Use RV32 Zba opcodes if possible. ... This commit adds optional support for selected Zba opcodes (address generation) to speed up Viper and native code generation on MCUs where those opcodes are supported (namely RP2350). Right now support for these opcodes is opt-in, as extension detection granularity on the RISC-V platform is still a bit in flux. Relying on the 'B' bit in the MISA register may yield both false positives and false negatives depending on the RISC-V implementation the check runs on. As a side-effect of Zba support, regular non-byte load/stores have been made shorter by two bytes. Whilst this makes code using Zba take up the same space as non-Zba code, the former will still be faster as it will have to process just one instruction instead of two, without stalling registers between the shift and the addition needed to compute the final offset. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-09-19 15:51:37 +02:00
Damien George	a3f9dec788	py/mpconfig: Enable the sys module at all feature levels by default. ... This is a pretty fundamental module, and even minimal ports like unix and zephyr minimal have it enabled. So, enabled it by default at the lowest feature level. Most things in the `sys` module are configurable, and off by default, so it shouldn't add too much to ports that don't already have it enabled (which is just the minimal port). Also note that `sys` is still disabled on the bare-arm port, to keep that ultra minimal. It means we now have bare-arm without `sys` and the minimal port with `sys`. That will allow different code size comparisons if/when new `sys` features are added. Signed-off-by: Damien George <damien@micropython.org>	2025-08-22 13:31:10 +10:00
Damien George	b5fcb33eaa	py/mpconfig: Enable CRYPTOLIB, HASHLIB_MD5, HASHLIB_SHA1 if SSL enabled. ... This commit unifies the configuration of MICROPY_PY_CRYPTOLIB, MICROPY_PY_HASHLIB_MD5 and MICROPY_PY_HASHLIB_SHA1, so they are enabled by default if MICROPY_PY_SSL is enabled. This matches the existing configuration of most of the ports. With this change, all ports remain the same except: - reneses-ra now enables MICROPY_PY_CRYPTOLIB, MICROPY_PY_HASHLIB_MD5 and MICROPY_PY_HASHLIB_SHA1. - rp2 now enables MICROPY_PY_HASHLIB_MD5. Signed-off-by: Damien George <damien@micropython.org>	2025-08-19 21:10:00 +10:00
Damien George	989abae12c	py/mpconfig: Move MICROPY_MODULE___ALL__ option to other module options. ... Signed-off-by: Damien George <damien@micropython.org>	2025-08-19 13:00:45 +10:00
Damien George	169d382248	py/mpconfig: Rename MICROPY_PY___FILE__ to MICROPY_MODULE___FILE__. ... For consistency with other module-related configuration options. Signed-off-by: Damien George <damien@micropython.org>	2025-08-19 13:00:45 +10:00
Jeff Epler	4614ee9e68	py/binary: Add MICROPY_PY_STRUCT_UNSAFE_TYPECODES. ... This adds a compile-time flag to disable some "unsafe" and non-standard typecodes in struct, array and related modules. This is useful to turn off when fuzzing, as improper use of these typecodes can crash MicroPython. Signed-off-by: Jeff Epler <jepler@gmail.com>	2025-08-12 14:34:19 +10:00
Damien George	7e8705fe2b	all: Bump version to 1.27.0-preview. ... Signed-off-by: Damien George <damien@micropython.org>	2025-08-10 08:42:11 +10:00
Damien George	4ce2dd2cda	all: Bump version to 1.26.0. ... Signed-off-by: Damien George <damien@micropython.org>	2025-08-09 23:31:31 +10:00
Yoctopuce dev	69ead7d98e	py/parse: Add support for math module constants and float folding. ... Add a new MICROPY_COMP_CONST_FLOAT feature, enabled by in mpy-cross and when compiling with MICROPY_CONFIG_ROM_LEVEL_CORE_FEATURES. The new feature leverages the code of MICROPY_COMP_CONST_FOLDING to support folding of floating point constants. If MICROPY_COMP_MODULE_CONST is defined as well, math module constants are made available at compile time. For example: _DEG_TO_GRADIANT = const(math.pi / 180) _INVALID_VALUE = const(math.nan) A few corner cases had to be handled: - The float const folding code should not fold expressions resulting into complex results, as the mpy parser for complex immediates has limitations. - The constant generation code must distinguish between -0.0 and 0.0, which are different even if C consider them as ==. This change removes previous limitations on the use of `const()` expressions that would result in floating point number, so the test cases of micropython/const_error have to be updated. Additional test cases have been added to cover the new repr() code (from a previous commit). A few other simple test cases have been added to handle the use of floats in `const()` expressions, but the float folding code itself is also tested when running general float test cases, as float expressions often get resolved at compile-time (with this change). Signed-off-by: Yoctopuce dev <dev@yoctopuce.com>	2025-08-01 13:35:44 +10:00
Yoctopuce dev	dbbaa959c8	py/formatfloat: Improve accuracy of float formatting code. ... Following discussions in PR #16666, this commit updates the float formatting code to improve the `repr` reversibility, i.e. the percentage of valid floating point numbers that do parse back to the same number when formatted by `repr` (in CPython it's 100%). This new code offers a choice of 3 float conversion methods, depending on the desired tradeoff between code size and conversion precision: - BASIC method is the smallest code footprint - APPROX method uses an iterative method to approximate the exact representation, which is a bit slower but but does not have a big impact on code size. It provides `repr` reversibility on >99.8% of the cases in double precision, and on >98.5% in single precision (except with REPR_C, where reversibility is 100% as the last two bits are not taken into account). - EXACT method uses higher-precision floats during conversion, which provides perfect results but has a higher impact on code size. It is faster than APPROX method, and faster than the CPython equivalent implementation. It is however not available on all compilers when using FLOAT_IMPL_DOUBLE. Here is the table comparing the impact of the three conversion methods on code footprint on PYBV10 (using single-precision floats) and reversibility rate for both single-precision and double-precision floats. The table includes current situation as a baseline for the comparison: PYBV10 REPR_C FLOAT DOUBLE current = 364688 12.9% 27.6% 37.9% basic = 364812 85.6% 60.5% 85.7% approx = 365080 100.0% 98.5% 99.8% exact = 366408 100.0% 100.0% 100.0% Signed-off-by: Yoctopuce dev <dev@yoctopuce.com>	2025-08-01 00:47:33 +10:00
Damien George	241ee163c0	py/objboundmeth: Add option to use mp_is_equal instead of == comparison. ... This option is needed for ports such as webassembly where objects are proxied and can be identical without being the same C pointer. Signed-off-by: Damien George <damien@micropython.org>	2025-07-31 11:38:35 +10:00
Anson Mansfield	d5dc554742	docs: Document PEP487 __set_name__ implementation. ... Signed-off-by: Anson Mansfield <amansfield@mantaro.com>	2025-07-29 09:44:26 +10:00
Jeff Epler	7493275918	py/mpconfig,ports: Define new HEX_FMT formatting macro. ... Signed-off-by: Jeff Epler <jepler@gmail.com>	2025-07-25 10:55:28 +10:00
Jeff Epler	59ee59901b	extmod/vfs_posix: Add MICROPY_VFS_POSIX_WRITABLE option. ... When this configuration flag is set, VfsPosix instances can be written. Otherwise, they will always be created "read only". This flag is useful when fuzzing micropython: Without VfsPosix, the fuzzing input script cannot be read; but with writable VfsPosix, fuzzing scripts can potentially perform undesired operations on the host filesystem. Signed-off-by: Jeff Epler <jepler@gmail.com>	2025-07-24 10:39:41 +10:00
Angus Gratton	9b7d85227e	extmod/mbedtls: Implement recommended DTLS features, make optional. ... - DTLS spec recommends HelloVerify and Anti Replay protection be enabled, and these are enabled in the default mbedTLS config. Implement them here. - To help compensate for the possible increase in code size, add a MICROPY_PY_SSL_DTLS build config macro that's enabled for EXTRA and above by default. This allows bare metal mbedTLS ports to use DTLS with HelloVerify support. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-07-23 15:47:16 +10:00
Yoctopuce dev	df05caea6c	shared/timeutils: Standardize supported date range on all platforms. ... This is code makes sure that time functions work properly on a reasonable date range, on all platforms, regardless of the epoch. The suggested minimum range is 1970 to 2099. In order to reduce code footprint, code to support far away dates is only enabled specified by the port. New types are defined to identify timestamps. The implementation with the smallest code footprint is when support timerange is limited to 1970-2099 and Epoch is 1970. This makes it possible to use 32 bit unsigned integers for all timestamps. On ARM4F, adding support for dates up to year 3000 adds 460 bytes of code. Supporting dates back to 1600 adds another 44 bytes of code. Signed-off-by: Yoctopuce dev <dev@yoctopuce.com>	2025-07-09 11:54:21 +10:00
Alessandro Gatti	2ab06b61b3	py/emitnative: Let emitters know the compiled entity's name. ... This commit introduces an optional feature to provide to native emitters the fully qualified name of the entity they are compiling. This is achieved by altering the generic ASM API to provide a third argument to the entry function, containing the name of the entity being compiled. Currently only the debug emitter uses this feature, as it is not really useful for other emitters for the time being; in fact the macros in question just strip the name away. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-07-04 16:07:04 +10:00
Yoctopuce dev	66c0148022	py/runtime: Add support for using __all__ in star import. ... When the symbol `__all__` is defined in a module, `mp_import_all()` should import all listed symbols into the global environment, rather than relying on the underscore-is-private default. This is the standard in CPython. Each item is loaded in the same way as if it would be an explicit import statement, and will invoke the module's `__getattr__` function if needed. This provides a straightforward solution for fixing star import of modules using a dynamic loader, such as `extmod/asyncio` (see issue #7266). This improvement has been enabled at BASIC_FEATURES level, to avoid impacting devices with limited ressources, for which star import is of little use anyway. Additionally, detailled reporting of errors during `__all__` import has been implemented to match CPython, but this is only enabled when ERROR_REPORTING is set to MICROPY_ERROR_REPORTING_DETAILED. Signed-off-by: Yoctopuce dev <dev@yoctopuce.com>	2025-06-23 16:05:12 +10:00
Alessandro Gatti	1006ed69f0	py/emitinlinextensa: Add the rest of LX3 opcodes to the assembler. ... This commit expands the Xtensa inline assembler to support most if not all opcodes available on the ESP8266 and LX3 Xtensa cores. This is meant as a stepping stone to add inline assembler support for the ESP32 and its LX6 core, along to windowed-specific opcodes and additional opcodes that are present only on the LX7 core (ESP32-S3 and later). New opcodes being added are covered by tests, and the provided tests were expanded to also include opcodes available in the existing implementation. Given that the ESP8266 space requirements are tighter than ESP32's, certain opcodes that won't be commonly used have been put behind a define to save some space in the general use case. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-05-29 12:12:39 +10:00
Alessandro Gatti	f47e214cdc	all: Rename the "NORETURN" macro to "MP_NORETURN". ... This commit renames the NORETURN macro, indicating to the compiler that a function does not return, into MP_NORETURN to maintain the same naming convention of other similar macros. To maintain compaitiblity with existing code NORETURN is aliased to MP_NORETURN, but it is also deprecated for MicroPython v2. This changeset was created using a similar process to decf8e6a8b ("all: Remove the "STATIC" macro and just use "static" instead."), with no documentation or python scripts to change to reflect the new macro name. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-05-13 10:36:47 +10:00
Damien George	d01a981a9b	py/mpconfig: Enable io.IOBase at core feature level. ... IOBase is quite an important building block of other parts of the system, such as `mpremote mount` and running .mpy and native tests. This feature costs +244 bytes of firmware size on ARM Thumb2 architectures, which is worth the cost for the extra features it enables. The change here means that `io.IOBase` is now enabled on all nrf boards, (previously it was only nRF52840 and nRF9160) and also B_L072Z_LRWAN1 (there is no change to other ports or boards). Signed-off-by: Damien George <damien@micropython.org>	2025-05-09 12:43:27 +10:00
Damien George	28901b2c30	all: Bump version to 1.26.0-preview. ... Signed-off-by: Damien George <damien@micropython.org>	2025-04-21 17:07:30 +10:00
Damien George	f498a16c7d	all: Bump version to 1.25.0. ... Signed-off-by: Damien George <damien@micropython.org>	2025-04-16 00:28:30 +10:00
Damien George	56e90cb60b	py/mpconfig: Enable 2-argument built-in next() at basic feature level. ... This is a pretty fundamental built-in and having CPython-compatible behaviour is beneficial. The code size increase is not much, and ports/boards can still disable it if needed to save space. Addresses issue #5384. Signed-off-by: Damien George <damien@micropython.org>	2025-03-27 11:51:58 +11:00
Damien George	89e6c58c80	extmod/modvfs: Add vfs.rom_ioctl function and its ioctl constants. ... This is a generic interface to allow querying and modifying the read-only memory area of a device, if it has such an area. Signed-off-by: Damien George <damien@micropython.org>	2025-03-06 12:52:35 +11:00
Damien George	c3a18d74eb	extmod/modmarshal: Add new marshal module. ... This commit implements a small subset of the CPython `marshal` module. It implements `marshal.dumps()` and `marshal.loads()`, but only supports (un)marshalling code objects at this stage. The semantics match CPython, except that the actual marshalled bytes is not compatible with CPython's marshalled bytes. The module is enabled at the everything level (only on the unix coverage build at this stage). Signed-off-by: Damien George <damien@micropython.org>	2025-02-11 16:54:20 +11:00
Damien George	a11ba7775e	py/persistentcode: Add mp_raw_code_save_fun_to_bytes. ... Serialises a bytecode function/generator to a valid .mpy as bytes. Signed-off-by: Damien George <damien@micropython.org>	2025-02-11 16:54:02 +11:00
Damien George	ceb8ba60b4	py/objfun: Implement function.__code__ and function constructor. ... This allows retrieving the code object of a function using `function.__code__`, and then reconstructing a function from a code object using `FunctionType(code_object)`. This feature is controlled by `MICROPY_PY_FUNCTION_ATTRS_CODE` and is enabled at the full-features level. Signed-off-by: Damien George <damien@micropython.org>	2025-02-11 16:51:50 +11:00
Damien George	62e821ccb8	py/objcode: Factor code object out into its own file. ... The `mp_obj_code_t` and `mp_type_code` code object was defined internally in both `py/builtinevex.c` and `py/profile.c`, with completely different implementations (the former very minimal, the latter quite complete). This commit factors these implementations into a new, separate source file, and allows the code object to have four different modes, selected at compile-time: - MICROPY_PY_BUILTINS_CODE_NONE: code object not included in the build. - MICROPY_PY_BUILTINS_CODE_MINIMUM: very simple code object that just holds a reference to the function that it represents. This level is used when MICROPY_PY_BUILTINS_COMPILE is enabled. - MICROPY_PY_BUILTINS_CODE_BASIC: simple code object that holds a reference to the proto-function and its constants. - MICROPY_PY_BUILTINS_CODE_FULL: almost complete implementation of the code object. This level is used when MICROPY_PY_SYS_SETTRACE is enabled. Signed-off-by: Damien George <damien@micropython.org>	2025-02-11 16:42:14 +11:00
Angus Gratton	4bcbe88e74	py: Add optional support for recursive mutexes, use for gc mutex. ... Enabled by default if using threading and no GIL This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-02-03 15:02:02 +11:00
Alessandro Gatti	268acb714d	py/emitinlinerv32: Add inline assembler support for RV32. ... This commit adds support for writing inline assembler functions when targeting a RV32IMC processor. Given that this takes up a bit of rodata space due to its large instruction decoding table and its extensive error messages, it is enabled by default only on offline targets such as mpy-cross and the qemu port. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-01-02 11:49:10 +11:00
Damien George	50637ff239	extmod/vfs_rom: Add VfsRom filesystem object. ... This commit defines a new ROMFS filesystem for storing read-only files that can be memory mapped, and a new VfsRom driver. Files opened from this filesystem support the buffer protocol. This allows naturally getting the memory-mapped address of the file using: - memoryview(file) - uctypes.addressof(file) Furthermore, if these files are .mpy files then their content can be referenced in-place when importing. Such imports take up a lot less RAM than importing from a normal filesystem. This is essentially dynamically frozen .mpy files, building on the revamped v6 .mpy file format. Signed-off-by: Damien George <damien@micropython.org>	2024-12-23 13:04:54 +11:00