Under4Mhz

My concern is that users won't think to go looking at compiler switches when they get an internal compiler error. It looks like a compiler bug. I think users will give up and go look for another compiler or wait for a future fix. It never once occured to me there might be a compiler switch to fix this. I assumed it was a compiler bug. I think it's better to be conservative and make sure the compiler always works by default. Make potentially breaking optimisation switches optional.

The --no-zp-spill flag fixes the problem. I'd be inclined to suggest to enable no-zp-spill as the default. I approve of speed optimisations, but in this case I would personally prefer that all my code compiles successfully without setting flags, even if it means it runs slightly slower. The code size is 16K, which is not huge. I'll enable this flag in my build system for everything from now on so it won't be an issue for me anymore. It would be great if we could simply move some variables out of...

This has been resolved. sdcc correctly shows an error now. Thanks

Pointer math on void * results in no change

stack overflow when using uitoa

Area ZP Length Error

I use pointers to structs a lot. I think this would be a great change to have.

Internal error: validateLink failed