Simple variable memory assignment fails about millfork HOT 3 CLOSED

I'm tempted to make volatile variables exempt from this optimization, but agreed, documenting this is a must.

from millfork.

The variables foo and bar are unused (because they are never read from), so the compiler removes them in order to save memory.

Did you plan on using those variables for debugging? As a temporary workaround, you can use arrays, as arrays are currently never optimized away.

from millfork.

The intended use case was indeed for debugging. I just happened to notice it when trying to build a minimal repro for another one of the other issues I filed. It makes sense that the variables would be optimized out, however, so I don't think there's anything to do here, except perhaps further documentation.

from millfork.