What about using Intel C++ Compiler for compiling? [CORE2337] #2761
Comments
|
Commented by: Don Young (clxbase) Ealier version of InterBase/FireBird give user a very good feeling: neat, simple, and green. In those version, IB/FB have very few files. Yet today, the engine is becoming more and more complicated in file structure, with too many dlls and additional files. |
|
Commented by: @dyemanov It has already been discussed. See here for example (scroll down until you see the thread mentioning Intel C++): |
|
Commented by: @dyemanov If you don't care about the binaries size or ability to fix bugs in the compiler run-time quickly, then it's possible to avoid the MS run-time hell even with MSVC. So this has no relationship with Intel C++, actually. And yes, this also has been discussed in fb-devel. BTW, it's recommended to suggest the improvements there before posting them into the tracker. |
Modified by: Sean Leyne (seanleyne)status: Open [ 1 ] => Resolved [ 5 ] resolution: Won't Fix [ 2 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Don Young (clxbase)
I think Intel's new C++ compiler should be more suitable for FireBird. Currently we compile firebird using MS VC8, which lead to a dependency on MSVCP80.dll and MSVCR80.dll for both FBClient.dll and the core engine. These 2 additional dlls make deployment of FB quite sluggish. So I think switching to Intel's compiler should be a good idea, which has already been adopted by MySQL. After we've switched FB codebase to Intel C++, we never need VC runtime dlls anymore, and at the same time, we gain more effeciency.
The text was updated successfully, but these errors were encountered: