WP 34S and 31S bugs and fixes

[Bit]

(12-24-2014 03:00 PM)Nigel (UK) Wrote:  

(12-24-2014 01:11 PM)Bit Wrote:  I couldn't reproduce this issue.

Which binary were you using? Did you compile it yourself? If so, which compiler did you use and what was in features.h?

I used the calc_full.bin binary. I compiled it myself; the gcc version is 4.8.1 from MinGW and 4.7.2 from the yagarto installation. (I'm doing this on Windows.) I'd need to look at the makefile to be sure which one is actually being used; you are probably much more familiar with this than I am. I haven't done anything with the compiler since I first installed it a couple of years ago. Before compiling I made a fresh checkout of version 3716 into a clean directory, making no changes to features.h before compiling.

Nigel (UK) (Edited for clarity)

As explained by Marcus earlier, and I can confirm based on my own experience, you shouldn't use anything but Yagarto GCC 4.6.0 because other builds or versions of GCC could create subtly broken binaries. Please check if you can reproduce the problem with Yagarto 4.6.0.

Edit: Those who use Yagarto under Linux with Wine will notice that compiling the constants (libconst.a) takes a lot of time. That's because GCC is invoked for some 107 small source files one at a time and starting up an application through Wine involves a lot of overhead. Since those files only have some very simple static data in them but no code, it makes no difference which GCC you use and you can change compile_consts.c to invoke a faster native GCC. I have verified that e.g. the CodeSourcery build of GCC 4.6.1 (which is known to create broken binaries otherwise) compiles the constants correctly and the .rodata sections (the only thing that matters) are completely identical to those produced by Yagarto 4.6.0.