|
|
|
/*
|
|
|
|
* This file is part of the MicroPython project, http://micropython.org/
|
|
|
|
*
|
|
|
|
* The MIT License (MIT)
|
|
|
|
*
|
|
|
|
* Copyright (c) 2013, 2014 Damien P. George
|
|
|
|
*
|
|
|
|
* Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
|
|
* of this software and associated documentation files (the "Software"), to deal
|
|
|
|
* in the Software without restriction, including without limitation the rights
|
|
|
|
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
|
|
* copies of the Software, and to permit persons to whom the Software is
|
|
|
|
* furnished to do so, subject to the following conditions:
|
|
|
|
*
|
|
|
|
* The above copyright notice and this permission notice shall be included in
|
|
|
|
* all copies or substantial portions of the Software.
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
|
|
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
|
|
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
|
|
* THE SOFTWARE.
|
|
|
|
*/
|
all: Unify header guard usage.
The code conventions suggest using header guards, but do not define how
those should look like and instead point to existing files. However, not
all existing files follow the same scheme, sometimes omitting header guards
altogether, sometimes using non-standard names, making it easy to
accidentally pick a "wrong" example.
This commit ensures that all header files of the MicroPython project (that
were not simply copied from somewhere else) follow the same pattern, that
was already present in the majority of files, especially in the py folder.
The rules are as follows.
Naming convention:
* start with the words MICROPY_INCLUDED
* contain the full path to the file
* replace special characters with _
In addition, there are no empty lines before #ifndef, between #ifndef and
one empty line before #endif. #endif is followed by a comment containing
the name of the guard macro.
py/grammar.h cannot use header guards by design, since it has to be
included multiple times in a single C file. Several other files also do not
need header guards as they are only used internally and guaranteed to be
included only once:
* MICROPY_MPHALPORT_H
* mpconfigboard.h
* mpconfigport.h
* mpthreadport.h
* pin_defs_*.h
* qstrdefs*.h
7 years ago
|
|
|
#ifndef MICROPY_INCLUDED_PY_EMITGLUE_H
|
|
|
|
#define MICROPY_INCLUDED_PY_EMITGLUE_H
|
|
|
|
|
|
|
|
#include "py/obj.h"
|
|
|
|
#include "py/bc.h"
|
|
|
|
|
|
|
|
// These variables and functions glue the code emitters to the runtime.
|
|
|
|
|
|
|
|
// These must fit in 8 bits; see scope.h
|
|
|
|
enum {
|
|
|
|
MP_EMIT_OPT_NONE,
|
|
|
|
MP_EMIT_OPT_BYTECODE,
|
|
|
|
MP_EMIT_OPT_NATIVE_PYTHON,
|
|
|
|
MP_EMIT_OPT_VIPER,
|
|
|
|
MP_EMIT_OPT_ASM,
|
|
|
|
};
|
|
|
|
|
|
|
|
typedef enum {
|
|
|
|
MP_CODE_UNUSED,
|
|
|
|
MP_CODE_RESERVED,
|
|
|
|
MP_CODE_BYTECODE,
|
|
|
|
MP_CODE_NATIVE_PY,
|
|
|
|
MP_CODE_NATIVE_VIPER,
|
|
|
|
MP_CODE_NATIVE_ASM,
|
|
|
|
} mp_raw_code_kind_t;
|
|
|
|
|
py: Add support to save native, viper and asm code to .mpy files.
This commit adds support for saving and loading .mpy files that contain
native code (native, viper and inline-asm). A lot of the ground work was
already done for this in the form of removing pointers from generated
native code. The changes here are mainly to link in qstr values to the
native code, and change the format of .mpy files to contain native code
blocks (possibly mixed with bytecode).
A top-level summary:
- @micropython.native, @micropython.viper and @micropython.asm_thumb/
asm_xtensa are now allowed in .py files when compiling to .mpy, and they
work transparently to the user.
- Entire .py files can be compiled to native via mpy-cross -X emit=native
and for the most part the generated .mpy files should work the same as
their bytecode version.
- The .mpy file format is changed to 1) specify in the header if the file
contains native code and if so the architecture (eg x86, ARMV7M, Xtensa);
2) for each function block the kind of code is specified (bytecode,
native, viper, asm).
- When native code is loaded from a .mpy file the native code must be
modified (in place) to link qstr values in, just like bytecode (see
py/persistentcode.c:arch_link_qstr() function).
In addition, this now defines a public, native ABI for dynamically loadable
native code generated by other languages, like C.
6 years ago
|
|
|
typedef struct _mp_qstr_link_entry_t {
|
|
|
|
uint16_t off;
|
|
|
|
uint16_t qst;
|
|
|
|
} mp_qstr_link_entry_t;
|
|
|
|
|
|
|
|
typedef struct _mp_raw_code_t {
|
|
|
|
mp_uint_t kind : 3; // of type mp_raw_code_kind_t
|
|
|
|
mp_uint_t scope_flags : 7;
|
|
|
|
mp_uint_t n_pos_args : 11;
|
|
|
|
const void *fun_data;
|
|
|
|
const mp_uint_t *const_table;
|
|
|
|
#if MICROPY_PERSISTENT_CODE_SAVE
|
|
|
|
size_t fun_data_len;
|
|
|
|
uint16_t n_obj;
|
|
|
|
uint16_t n_raw_code;
|
|
|
|
#if MICROPY_PY_SYS_SETTRACE
|
|
|
|
mp_bytecode_prelude_t prelude;
|
|
|
|
// line_of_definition is a Python source line where the raw_code was
|
|
|
|
// created e.g. MP_BC_MAKE_FUNCTION. This is different from lineno info
|
|
|
|
// stored in prelude, which provides line number for first statement of
|
|
|
|
// a function. Required to properly implement "call" trace event.
|
|
|
|
mp_uint_t line_of_definition;
|
|
|
|
#endif
|
|
|
|
#if MICROPY_EMIT_MACHINE_CODE
|
py: Add support to save native, viper and asm code to .mpy files.
This commit adds support for saving and loading .mpy files that contain
native code (native, viper and inline-asm). A lot of the ground work was
already done for this in the form of removing pointers from generated
native code. The changes here are mainly to link in qstr values to the
native code, and change the format of .mpy files to contain native code
blocks (possibly mixed with bytecode).
A top-level summary:
- @micropython.native, @micropython.viper and @micropython.asm_thumb/
asm_xtensa are now allowed in .py files when compiling to .mpy, and they
work transparently to the user.
- Entire .py files can be compiled to native via mpy-cross -X emit=native
and for the most part the generated .mpy files should work the same as
their bytecode version.
- The .mpy file format is changed to 1) specify in the header if the file
contains native code and if so the architecture (eg x86, ARMV7M, Xtensa);
2) for each function block the kind of code is specified (bytecode,
native, viper, asm).
- When native code is loaded from a .mpy file the native code must be
modified (in place) to link qstr values in, just like bytecode (see
py/persistentcode.c:arch_link_qstr() function).
In addition, this now defines a public, native ABI for dynamically loadable
native code generated by other languages, like C.
6 years ago
|
|
|
uint16_t prelude_offset;
|
|
|
|
uint16_t n_qstr;
|
|
|
|
mp_qstr_link_entry_t *qstr_link;
|
|
|
|
#endif
|
|
|
|
#endif
|
|
|
|
#if MICROPY_EMIT_MACHINE_CODE
|
|
|
|
mp_uint_t type_sig; // for viper, compressed as 2-bit types; ret is MSB, then arg0, arg1, etc
|
|
|
|
#endif
|
|
|
|
} mp_raw_code_t;
|
|
|
|
|
|
|
|
mp_raw_code_t *mp_emit_glue_new_raw_code(void);
|
|
|
|
|
|
|
|
void mp_emit_glue_assign_bytecode(mp_raw_code_t *rc, const byte *code,
|
|
|
|
#if MICROPY_PERSISTENT_CODE_SAVE || MICROPY_DEBUG_PRINTERS
|
|
|
|
size_t len,
|
|
|
|
#endif
|
|
|
|
const mp_uint_t *const_table,
|
|
|
|
#if MICROPY_PERSISTENT_CODE_SAVE
|
|
|
|
uint16_t n_obj, uint16_t n_raw_code,
|
|
|
|
#endif
|
|
|
|
mp_uint_t scope_flags);
|
py: Add support to save native, viper and asm code to .mpy files.
This commit adds support for saving and loading .mpy files that contain
native code (native, viper and inline-asm). A lot of the ground work was
already done for this in the form of removing pointers from generated
native code. The changes here are mainly to link in qstr values to the
native code, and change the format of .mpy files to contain native code
blocks (possibly mixed with bytecode).
A top-level summary:
- @micropython.native, @micropython.viper and @micropython.asm_thumb/
asm_xtensa are now allowed in .py files when compiling to .mpy, and they
work transparently to the user.
- Entire .py files can be compiled to native via mpy-cross -X emit=native
and for the most part the generated .mpy files should work the same as
their bytecode version.
- The .mpy file format is changed to 1) specify in the header if the file
contains native code and if so the architecture (eg x86, ARMV7M, Xtensa);
2) for each function block the kind of code is specified (bytecode,
native, viper, asm).
- When native code is loaded from a .mpy file the native code must be
modified (in place) to link qstr values in, just like bytecode (see
py/persistentcode.c:arch_link_qstr() function).
In addition, this now defines a public, native ABI for dynamically loadable
native code generated by other languages, like C.
6 years ago
|
|
|
|
|
|
|
void mp_emit_glue_assign_native(mp_raw_code_t *rc, mp_raw_code_kind_t kind, void *fun_data, mp_uint_t fun_len,
|
|
|
|
const mp_uint_t *const_table,
|
|
|
|
#if MICROPY_PERSISTENT_CODE_SAVE
|
|
|
|
uint16_t prelude_offset,
|
|
|
|
uint16_t n_obj, uint16_t n_raw_code,
|
|
|
|
uint16_t n_qstr, mp_qstr_link_entry_t *qstr_link,
|
|
|
|
#endif
|
|
|
|
mp_uint_t n_pos_args, mp_uint_t scope_flags, mp_uint_t type_sig);
|
|
|
|
|
|
|
|
mp_obj_t mp_make_function_from_raw_code(const mp_raw_code_t *rc, mp_obj_t def_args, mp_obj_t def_kw_args);
|
|
|
|
mp_obj_t mp_make_closure_from_raw_code(const mp_raw_code_t *rc, mp_uint_t n_closed_over, const mp_obj_t *args);
|
|
|
|
|
all: Unify header guard usage.
The code conventions suggest using header guards, but do not define how
those should look like and instead point to existing files. However, not
all existing files follow the same scheme, sometimes omitting header guards
altogether, sometimes using non-standard names, making it easy to
accidentally pick a "wrong" example.
This commit ensures that all header files of the MicroPython project (that
were not simply copied from somewhere else) follow the same pattern, that
was already present in the majority of files, especially in the py folder.
The rules are as follows.
Naming convention:
* start with the words MICROPY_INCLUDED
* contain the full path to the file
* replace special characters with _
In addition, there are no empty lines before #ifndef, between #ifndef and
one empty line before #endif. #endif is followed by a comment containing
the name of the guard macro.
py/grammar.h cannot use header guards by design, since it has to be
included multiple times in a single C file. Several other files also do not
need header guards as they are only used internally and guaranteed to be
included only once:
* MICROPY_MPHALPORT_H
* mpconfigboard.h
* mpconfigport.h
* mpthreadport.h
* pin_defs_*.h
* qstrdefs*.h
7 years ago
|
|
|
#endif // MICROPY_INCLUDED_PY_EMITGLUE_H
|