We had the same thing with C when we were benchmarking it against B3D once... the code was set up to perform a number of mathematical operations something like ten million times, and see how long it took. It looked like C was phenomenally fast until we realised that, because the results of the calculations were never actually used for anything, the compiler was completely ignoring them and we were testing nothing!
Compiler Bloat
Miscellaneous Forums/General Discussion/Compiler BloatThe forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.