Re: WP 34S New Build with older GCC Message #5 Posted by Marcus von Cube, Germany on 22 June 2013, 5:12 p.m., in response to message #4 by Andrew Nikitin
First of all, thanks for the tests.
To answer your question: We are using the most effective space optimization GCC offers. In an earlier phase of the project, I've had a try with the CodeSourcery GCC version that offers better optimizations. This compiler produced strange failures in parts of the code which made me revert to Yagarto GCC which proved to produce more stable code. Some GCC updates introduced by the CodeSourcery team may have been ported to the GCC main trunk (or any similar "improvements"), breaking the code generator in our special case. It's just a guess but when strange things happen in code that once used to work I think it's a good idea to check if a compiler release may have introduced the bug.
The handling of unallocated local registers in the LINEQ code may still cause strange effects due to coding errors from our side. I have to check my code. Debugging this on the hardware is almost impossible because I need to debug optimized code which is simply not designed for this.
|