Hi, I had some problems with the gcc compiler in BeOS again - looks like it can compile BFS correctly only with -O1. When looking over our Jamrules, I saw that the whole testing suite is build with -O0 -g - but having made the experiences with a non- functional optimization in gcc, I would heavily suggest to not do this always. I would compile the test suite with the same compiler options as the release build will, so that bugs caused by the compiler can also be found in the future. At least, this would give us additional security that gcc's output is correct. If some strange bugs show up, we can always fall back to -g -O0 to fix them. What do you think? Adios... Axel.