User forums > General (but related to Code::Blocks)
GCC 4.1.1 for MinGW
JacK-DuRdEn_:
--- Quote from: jarro_2783 on June 02, 2006, 03:36:39 am ---so it's not that there has been a change in the way c++ works, it's that such a huge upgrade of something like a compiler is bound to cause bugs?
--- End quote ---
exactly. as far as i know there aren't changes in the way c++ (or any language for that matter) for looong years. any project of great magnitude like a compiler is bound to have regressions and compatibility problems with the way thing were done before. that's why they release beta versions and make release candidates etc.
Balazs:
Just to add a little info:
GCC 4 optimizes MUCH better, than any 3.x version. I have written an image processing plugin for avisynth some time ago, and compiled with gcc 4 with -march=pentium3 -O3, it as about 2 times faster, than compiled with the EXACT same flags with gcc 3.4.5
I have also read about this, that gcc 4 uses much more modern and robust optimization techniques, and my results only confirm this.
Another thing:
Why is it needed to install gcc 4 to C:\MinGW? I tried in other directory, where I prefer, but there it cannot find it's own includes and libs. How come? Is C:\MinGW hard coded into g++.exe? (I hope not)
--
Greets,
B.
sethjackson:
--- Quote from: Balazs on June 05, 2006, 12:55:40 am ---Another thing:
Why is it needed to install gcc 4 to C:\MinGW? I tried in other directory, where I prefer, but there it cannot find it's own includes and libs. How come? Is C:\MinGW hard coded into g++.exe? (I hope not)
--
Greets,
B.
--- End quote ---
No it is not hard coded. You just need to tell C::B where to look for GCC 4. :)
Ceniza:
It seems the path for includes and libs gets hardcoded somewhere in the compilation process. I don't know the reason it happens but it does.
Checking g++.exe from GCC 4.1.1, there's a C:/MinGW hardcoded into it, and checking g++.exe from GCC 3.4.5 there's no path at all there, but just changing that won't fix it.
Michael:
--- Quote from: sethjackson on June 05, 2006, 01:15:39 am ---
--- Quote from: Balazs on June 05, 2006, 12:55:40 am ---Another thing:
Why is it needed to install gcc 4 to C:\MinGW? I tried in other directory, where I prefer, but there it cannot find it's own includes and libs. How come? Is C:\MinGW hard coded into g++.exe? (I hope not)
--
Greets,
B.
--- End quote ---
No it is not hard coded. You just need to tell C::B where to look for GCC 4. :)
--- End quote ---
Hello,
Ceniza is right.
The first time I have tried GCC 4.1.0 in a MinGW not installed in C:\, I got several troubles to make it works with C::B. Since I installed MinGW in C:\ all works like a charm (no need for special tricks).
Best wishes,
Michael
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version