Ayke

> There's a directive in the PIO language to force the origin `.origin ` - so if we don't support it, there'll be some subset of PIO code we can't...

Yes, I'm aware of those. Those flags aren't actually passed to the linker but these symbols are part of mingw-w64 (and are duplicated there).

This is fixed upstream: https://github.com/mingw-w64/mingw-w64/commit/8526cb618269440a94810b94b77f8bd48c5c3396 We could update now, or wait until the next mingw-w64 release. I think it's fine to wait, the message is annoying but harmless.

I agree this is a bug and should be fixed. When we looked at the problem it appears that a LLVM pass is going wrong, it somehow hangs and eats...

Here is a fix: https://github.com/tinygo-org/tinygo/pull/3164

> Be a good time to define the API for deep sleep. There are many kinds of "deep sleep". Making an API that works for all is very difficult. Especially...

No, this is not yet supported. I think it would be nice if this is implemented not with an `-extra` flag but by accepting multiple "package names" during the build,...

> I noticed there is an open PR #861 for doing something similar. The design approach is nice, however the code generation for registering interrupts is an odd choice since...

I have hit a more general problem too. Enabling the UART on Nordic chips means a lot of current is constantly consumed. I fixed this in a battery powered application...

Strawman proposal: add a `-output` flag to the compiler which can be set as needed (`-output=usb`, `-output=uart`, `-output=none`). The builder will set a build tag accordingly, such as `output.uart`. This...