As Curtis Maloney wrote:
> The new code called it twice, with different values. So the
> inline-able function was not inlined, and thus the constant
> wasn't cleaned up.
Ouch.
> I fixed this by giving the function declaration
> __attribute__((always_inline))...
Yes, that's a
Now, I've been working so far on the assumption that avr-libc is developed
solely for use with GCC. So it's not a problem to use GCC-sisms in the headers.
I today ran into a problem with _delay_ms(), where it brought in the floating
point code. This I found odd, because my project had used
