Now that some ports support multiple architectures (eg esp32 has both Xtensa and RISC-V CPUs) it's no longer possible to set mpy-cross flags based on the target, eg `./run-tests.py --target esp32`. Instead this commit makes it so the `-march=xxx` argument to mpy-cross is detected automatically via evaluation of `sys.implementation._mpy`. Signed-off-by: Damien George <damien@micropython.org> |
||
|---|---|---|
| .. | ||
| async_check.py | ||
| async_check.py.exp | ||
| bytearray.py | ||
| bytearray.py.exp | ||
| byteorder.py | ||
| byteorder.py.exp | ||
| complex.py | ||
| complex.py.exp | ||
| const.py | ||
| const.py.exp | ||
| coverage.py | ||
| coverage.py.exp | ||
| float.py | ||
| float.py.exp | ||
| fstring.py | ||
| fstring.py.exp | ||
| inlineasm_thumb2.py | ||
| inlineasm_thumb2.py.exp | ||
| int_big.py | ||
| int_big.py.exp | ||
| io_module.py | ||
| io_module.py.exp | ||
| native_check.py | ||
| native_check.py.exp | ||
| README | ||
| repl_emacs_check.py | ||
| repl_emacs_check.py.exp | ||
| repl_words_move_check.py | ||
| repl_words_move_check.py.exp | ||
| reverse_ops.py | ||
| reverse_ops.py.exp | ||
| set_check.py | ||
| set_check.py.exp | ||
| slice.py | ||
| slice.py.exp | ||
| target_info.py | ||
| target_info.py.exp | ||
This directory doesn't contain real tests, but code snippets to detect various interpreter features, which can't be/inconvenient to detect by other means. Scripts here are executed by run-tests.py at the beginning of testsuite to decide what other test groups to run/exclude.