atmel-samd: Big integer support

[tdicola]

Filing an issue to remember, let's investigate big integer (> 31 bit values) support for the samd21 port. In some discussion we think it's turned off right now and would fail. Let's see what the impact would be to turn on and support. It's not a super common case but core python does support arbitrary size integers. Won't be as fast as the optimized 31-bit packed int values, but would let people port desktop python code over with less surprises when numbers get big.

[willingc]

Yep. Just ran into this when going through the 8266 REPL tutorial with the samd.

>>> 12**34
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OverflowError: small int overflow
>>>

[tannewt]

FYI, @willingc the latest docs are here: https://circuitpython.readthedocs.io/en/latest/index.html The tutorial still has that issue but the API docs will be more up to date. I need to clean that other tutorial stuff up. My intention is for ReadTheDocs to be mostly reference and use the Adafruit Learning System for tutorials and guides.

…

On Fri, Mar 24, 2017 at 10:13 PM Carol Willing ***@***.***> wrote: Yep. Just ran into this when going through the [8266 REPL tutorial}( https://adafruit-micropython.readthedocs.io/en/latest/docs/esp8266/tutorial/repl.html#using-the-repl) with the samd. >>> 12**34 Traceback (most recent call last): File "<stdin>", line 1, in <module> OverflowError: small int overflow >>> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#110 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADNqUYyEIXTmoAiAtnqI9cYZo9dpmsiks5rpEADgaJpZM4MV1ix> .

[tannewt]

Does anyone know of any specific use cases where we need this? OneWire 64 bit ids is one place they could be handy.

The MPZ implementation adds ~5000 bytes to the Feather M0 express build. The longlong implementation is ~3000 bytes. We have ~80 bytes left on the Arduino Zero build. I'd hate to split functionality between express/non-express so starkly.

[tannewt]

I'll turn this on for the SAMD51 boards with #178.

[tannewt]

Looks like enabling a LONGINT impl will break our mpys. Maybe we can change this so they are compatible?

[dhalbert]

Looks like enabling a LONGINT impl will break our mpys. Maybe we can change this so they are compatible?

After looking at this, I think this is not going to be an issue. mpy-cross is already set to use MICROPY_LONGINT_IMPL_MPZ for all the .mpy's it produces, so that will not change by turning on longints in our port. tools/mpy-tool.py cares about whether the implementation supports longints or not, but it's used to build internal frozen modules, not .mpy files.

[tannewt]

OK perfect! That should make it easy.

…

On Mon, Oct 9, 2017 at 6:42 PM Dan Halbert ***@***.***> wrote: Looks like enabling a LONGINT impl will break our mpys. Maybe we can change this so they are compatible? After looking at this, I think this is not going to be an issue. mpy-cross is already set to use MICROPY_LONGINT_IMPL_MPZ for all the .mpy's it produces, so that will not change by turning on longints in our port. tools/mpy-tool.py cares about whether the implementation supports longints or not, but it's used to build internal frozen modules, not .mpy files. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#110 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADNqRPEKSdovMPDvz-aq3V1F0Uroa6Rks5sqst-gaJpZM4MV1ix> .