08-06-2012, 08:46 PM
I figured out what the problem was. Well, that is unbelievable!
Both Caves.cpp and Ravines.cpp define a structure that is used for temporary point storage, cDefPoint. That structure was used only inside each module respectively. But for some reason, gcc joined the handling of those two structures together when optimizing, although one structure is 20 bytes and the other is only 16 bytes. And that's why getting the vector's size failed - it was dividing by the incorrect amount of bytes. Unfortunately that coupled with another gcc optimization that replaces division with multiplication and some binary magic, so the final numbers were so off that one couldn't recognize the problem.
Fixed in rev 714 (we have "Raspberry Pi" in the commit messages, yay!
Both Caves.cpp and Ravines.cpp define a structure that is used for temporary point storage, cDefPoint. That structure was used only inside each module respectively. But for some reason, gcc joined the handling of those two structures together when optimizing, although one structure is 20 bytes and the other is only 16 bytes. And that's why getting the vector's size failed - it was dividing by the incorrect amount of bytes. Unfortunately that coupled with another gcc optimization that replaces division with multiplication and some binary magic, so the final numbers were so off that one couldn't recognize the problem.
Fixed in rev 714 (we have "Raspberry Pi" in the commit messages, yay!