We are near a final relase of our code so I try to recompiler our projet
with -O3. With this level of optimization many of our source files doesn’t
compile. We get theses errors from gcc.
…/PteManager.cpp:815: Internal compiler error.
…/PteManager.cpp:815: Please submit a full bug report.
…/PteManager.cpp:815: See
URL:http://www.gnu.org/software/gcc/faq.html#bugreport for instructions.
Here is the compiler flag we are using.
RELEASE = -O3 -DNDEBUG
$(MYDEFINES) -w8 -Wc,-mcpu=pentium,-march=pentium,-fno-pic,-fomit-frame-poin
ter,-freg-struct-return
Is anybody saw theses errors? What level of optimization most people are
using?
Thanks
Rejean Senecal
I bet if you double your PC’s RAM, this problem will go away.
Rejean Senecal <rsenecal@oerlikon.ca-no-spam> wrote:
We are near a final relase of our code so I try to recompiler our projet
with -O3. With this level of optimization many of our source files doesn’t
compile. We get theses errors from gcc.
./PteManager.cpp:815: Internal compiler error.
./PteManager.cpp:815: Please submit a full bug report.
./PteManager.cpp:815: See
URL:> http://www.gnu.org/software/gcc/faq.html#bugreport> > for instructions.
Here is the compiler flag we are using.
RELEASE = -O3 -DNDEBUG
$(MYDEFINES) -w8 -Wc,-mcpu=pentium,-march=pentium,-fno-pic,-fomit-frame-poin
ter,-freg-struct-return
Is anybody saw theses errors? What level of optimization most people are
using?
Thanks
Rejean Senecal
Rejean Senecal wrote:
We are near a final relase of our code so I try to recompiler our projet
with -O3. With this level of optimization many of our source files doesn’t
compile. We get theses errors from gcc.
From personnel experience, you should not go more than -O2. If you want your
code to be faster add the -march=pentium to your gcc option or
-Wc,-march=pentium to qcc. You will then use the pentium instruction set (
instead of 386 ) and it realignes the code to optimize the dual instruction
pipelines, it is specialy noticable on floating point manipulation.
Michel Belanger