Comparison QB64 compiled with gcc optimizations and without
#46
> QB64 should it be compiled with the -O3 option by default?

> Are the results the same on Linux, macOS and Windows?
> What are the Pros Vs Cons?


There's two aspect that I think need to be considered: technical, and practical.

From the technical side, I'm still hesitant to recommend it as there are some coding patterns in
libqb.cpp
that are very likely to get optimized wrong, resulting in a broken program. It does appear that this isn't as big of a problem as I first assumed it would be, as we do have several successful uses of it, but I still don't think it makes sense as a default just yet.

From the practical side, QB64 itself probably shouldn't be compiled with
-O3
due to the length of time and amount of memory it can take. I haven't tried it on Linux (I think the situation might be much better) but on Windows it ends up taking several GBs of RAM and many minutes (10 or 15) to finish compiling. For Linux and MacOS, since they have to build QB64 themselves during the setup script I think that's just too long to expect people to sit through.
Reply


Messages In This Thread
RE: Comparison QB64 compiled with Ofast and without - by DSMan195276 - 06-14-2022, 01:31 AM



Users browsing this thread: 20 Guest(s)