| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
I.e. with its own globals. So, just as for functions, we need to switch
globals when resuming a generator.
|
| |
|
|
|
|
|
|
|
| |
This follows pattern already used for objtuple, etc.: objfun.h's content
is not public - each and every piece of code should not have access to it.
It's not private either - with out architecture and implementation language
(C) it doesn't make sense to keep implementation of each object strictly
private and maintain cumbersome accessors. It's "local" - intended to be
used by a small set of "friend" (in C++ terms) objects.
|
| |
|
|
| |
Addresses issue #487.
|
| |
|
|
|
| |
Any generated headers go in $(BUILD)/genhdr/, and are #included as
'genhdr/xxx.h'.
|
| |\
| |
| |
| | |
lurch-relocatable-build-dir
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
The autogenerated header files have been moved about, and an extra
include dir has been added, which means you can give a custom
BUILD=newbuilddir option to make, and everything "just works"
Also tidied up the way the different Makefiles build their include-
directory flags
|
| |\ \
| | |
| | | |
nlr: Add implementation using setjmp/longjmp.
|
| | |/
| |
| |
| |
| | |
Having an optimized asm implementation is good, but if we want portability,
that's it.
|
| |\ \ |
|
| | |\ \
| | |/
| |/| |
Remove generated .h file if the generation process fails.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Not all functions implemented. Not enabled on pyboard.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Things get tricky when using the nlr code to catch exceptions. Need to
ensure that the variables (stack layout) in the exception handler are
the same as in the bit protected by the exception handler.
Prior to this patch there were a few bugs. 1) The constant
mp_const_MemoryError_obj was being preloaded to a specific location on
the stack at the start of the function. But this location on the stack
was being overwritten in the opcode loop (since it didn't think that
variable would ever be referenced again), and so when an exception
occurred, the variable holding the address of MemoryError was corrupt.
2) The FOR_ITER opcode detection in the exception handler used sp, which
may or may not contain the right value coming out of the main opcode
loop.
With this patch there is a clear separation of variables used in the
opcode loop and in the exception handler (should fix issue (2) above).
Furthermore, nlr_raise is no longer used in the opcode loop. Instead,
it jumps directly into the exception handler. This tells the C compiler
more about the possible code flow, and means that it should have the
same stack layout for the exception handler. This should fix issue (1)
above. Indeed, the generated (ARM) assembler has been checked explicitly,
and with 'goto exception_handler', the problem with &MemoryError is
fixed.
This may now fix problems with rge-sm, and probably many other subtle
bugs yet to show themselves. Incidentally, rge-sm now passes on
pyboard (with a reduced range of integration)!
Main lesson: nlr is tricky. Don't use nlr_push unless you know what you
are doing! Luckily, it's not used in many places. Using nlr_raise/jump
is fine.
|
| |/ / |
|
| | | |
|
| |/ |
|
| |\
| |
| | |
Move entry_table to separated header file.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
I was too hasty. Still a one-liner though.
|
| |/
|
|
| |
A one-liner, added especially for @pfalcon :)
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
That was easy - just avoid erroring out on seeing candidate dir for namespace
package. That's far from being complete though - namespace packages should
support importing portions of package from different sys.path entries, here
we require first matching entry to contain all namespace package's portions.
And yet, that's a way to put parts of the same Python package into multiple
installable package - something we really need for *Micro*Python.
|
| | | |
|
| |/ |
|
| |\
| |
| | |
Don't allow both ENDIANNESSes to be set
|
| | |
| |
| |
| |
| | |
See discussion on https://github.com/micropython/micropython/commit/2da81fa80c4cd965f05ad237d81d9764322fde20
Explicitly set `MP_ENDIANNESS_LITTLE` because that's the #define that is used in code elsewhere.
|
| | |
| |
| |
| | |
Disabled by default. Enabled in unix port.
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
| |
The logic appears to be that (at least beginning of) sys.versions is the
version of reference Python language implemented, not version of particular
implementation.
Also, bump set versions at 3.4.0, based on @dpgeorge preference.
|
| |
|
|
|
| |
Similar to tuples, lists, dicts. Statically allocated strings don't have hash
computed.
|
| |
|
|
|
| |
This feature was proposed with initial hashing RFC, and is prerequisite for
seamless static str object definition.
|
| | |
|
| | |
|
| |
|
|
| |
Enabled by MICROPY_ENABLE_PROPERTY.
|
| | |
|
| | |
|
| |
|
|
| |
Should address issue #475.
|
| |\ |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| | |
py: don't look for any additional headers when lexerunix is disabled
|
| | | |
|
| |\ \
| | |
| | | |
py: the entire `<unistd.h>` shouldn't be needed
|
| | |/ |
|
| | | |
|
| | | |
|
