User forums > General (but related to Code::Blocks)
BLITZ support?
Ptomaine:
The compilation time may be speeded up to 4 times by this approach.
Moreover, BLITZ lets a compiler to see all source code files as a single 'blitz' object and the compiler may optimize it more thoroughly.
What do you think?
Michael:
--- Quote from: Ptomaine on December 05, 2005, 03:51:51 pm ---The compilation time may be speeded up to 4 times by this approach.
Moreover, BLITZ lets a compiler to see all source code files as a single 'blitz' object and the compiler may optimize it more thoroughly.
What do you think?
--- End quote ---
Sorry for my ignorance, but what is BLITZ :?? I have searched for it by using Google, but have not found anything relevant.
Thank you.
Michael
takeshimiya:
I don't know about BLITZ, but there's some technologies in Apple Xcode IDE when using GCC that are just amazing regarding compile speed optimization:
Predictive Compilation
Xcode will even begin compiling a source code file while you are editing it. It begins reading in and parsing headers, making progress compiling the file even before you initiate a build. When you do choose to save and build the file, much of the work has already been compiled.
ZeroLink
Intended for use during development, it lets you bypass the linker, and instead have the executable load the .o files as needed.
Fix and Continue
Lets you make a change to one file, recompile it, and load it into the running executable, WITHOUT quitting, relinking, and relaunching the whole thing.
Distributed builds
Distributes compilation tasks among multiple computers on a network, and takes in account dual processors also.
Question: Do you think, at least in a distant future, that these features will be feasible in Code::Blocks?
Michael:
--- Quote from: Takeshi Miya on December 05, 2005, 05:52:15 pm ---I don't know about BLITZ, but there's some technologies in Apple Xcode IDE when using GCC that are just amazing regarding compile speed optimization:
Predictive Compilation
Xcode will even begin compiling a source code file while you are editing it. It begins reading in and parsing headers, making progress compiling the file even before you initiate a build. When you do choose to save and build the file, much of the work has already been compiled.
ZeroLink
Intended for use during development, it lets you bypass the linker, and instead have the executable load the .o files as needed.
Fix and Continue
Lets you make a change to one file, recompile it, and load it into the running executable, WITHOUT quitting, relinking, and relaunching the whole thing.
Distributed builds
Distributes compilation tasks among multiple computers on a network, and takes in account dual processors also.
Question: Do you think, at least in a distant future, that these features will be feasible in Code::Blocks?
--- End quote ---
Apple Xcode IDE technologies are really interesting and it would be cool if C::B will support them in the future :). Anyway, I have a doubt. C::B actually supports several compilers. Therefore to implement such technologies for all the supported compilers would be a huge work. And to implement them just for GCC would probably make C::B users to switch to GCC compiler and neglect the others. As a consequence, it would not make a lot of sense for C::B to maintain several compilers if the users just work with GCC...
Michael
takeshimiya:
Well, if you worry about that, currently precompiled headers in C::B RC2 are suported for GCC only, and I see lot's of people here using other compilers too.
But nothing stops to implement precompiled headers and the other features for other compilers, in fact I think they will be supported also.
Navigation
[0] Message Index
[#] Next page
Go to full version