Comment 2 for bug 1530165

Hi Thomas

Thank you for the info. Indeed, using 5-2015q4 does fix this error, but produces something similar elsewhere in our code. I've created another bug report for that, #1530664.

Are there any work-arounds for this? The problems occur in a large code base, and without optimizations the code is simply too slow for our microcontroller. I've been able to make things work using 4.9, but it involves hand-tuning some functions (i.e. replacing for-loops with repeated code), and is very fragile (since small, seemingly unrelated changes will bring back the error).

Cheers
Mark