Help needed in debugging AVR compilation errors about tinygo HOT 6 CLOSED

I have seen the second error more often. It is due to a limitation in the AVR backend (it cannot deal with struct parameters, and []byte is really a {ptr, len, cap} struct). See #20 for details. A temporary (ugly) workaround is to make the inliner more likely to run by increasing the value of the third parameter to Optmize(opt, size, inliner) in main.go.

I haven't seen the first error before but it also looks like an unimplemented feature.

from tinygo.

Boosted Optimize() 3 param as you suggested. the value 300 compiles (both errors go away) but does not execute as desired.

You are probably not surprised. Digging here to figure out more.

from tinygo.

You could try again now. The second problem is probably fixed with fdfa810. The first problem should really be fixed in upstream LLVM, but might also be fixed as a side effect (who knows).

A trick that might fix the first problem (again, a dirty workaround) is to sleep the same time everywhere. The optimizer will recognize the pattern and do the expensive int64 calculation at compile time.

from tinygo.

Ah now I see. The trouble with the second uncommented line might be related to the memory allocator, which I have never tested on AVR (as it wasn't able to run any significant programs).

from tinygo.

You were correct that changing all of the calls to time.Sleep() to use the same value let the compiler run without errors and without changing the value of the inliner param to Optimize(). That is probably not a practical long-term solution, of course.

The latest version of master lets the compiler run using various different time values like my original code, with the inline param set to the lower value 50.

from tinygo.

The latest version of master now is able to run the AVR I2C code with no change to the Optimize() function. I am going to close this issue as the original problem has been addressed. Thank you!

from tinygo.