Version 7 does offer some performance gains (especially in regards to optimized code for Pentium4 compared to GCC), but the debugger is less than stellar, LinuxJournal says.
Testing the Intel C++ Compiler
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
If your’re using VS.Net 7.x with this, just forget using it with the bundled STL in MSVC.Net. You’ll have to use STLport to get any decent STL support in ICL.
It is available on Windoze, for those who not know it.
-magg
I can’t get to the article for some reason but i have heard that the intel compiler for linux is tight. As it should be what better compilier to use then the one offered by the CPU manufacturer. This may be the primer that sets off a new level of quality software for linux. Where do i get my intel optimized and compiled linux kernel? GNU G++ does a pretty good job but still alot of it is guess work.
Dinkumware, P.J. Plauger’s company, makes an excellent C++ standard libary (incl STL) with support for VC++ and Intel C++ ::
Dinkum Unabridged Library for VC++
The Dinkum Unabridged Library V4.02 for VC++ is the successor to our highly popular V3.08 upgrade library for VC++ V6.0 and our libraries for Windows CE. In one package, you get support for VC++ V6.0, V7.0 (.NET), and V7.1 (Everett or .NET 2003), as well as the Intel C++ compiler for Windows. You get our industry-leading Standard C++, Abridged, and EC++ libraries — with optional iterator debugging, multithreading, exception handling, and namespaces. You can use them with the existing VC++ C library, our C95 library or our C99 library. It’s a natural companion to our highly portable Dinkum Unabridged Library, which works with most other popular compilers.
http://dinkumware.com/libdual_vc.html
The thing is, I don’t do heavy development, so I am certainly not willing to pay 400 bucks for a compiler. Once the evaluation period ends, you’ll be screwed because of the incompatibility.
As I installed gentoo I saw that it can be configured to compile its packages using icc. There was however a note stating tha not all of them are suitable for this trick.
As I installed gentoo I saw that it can be configured to compile its packages using icc. There was however a note stating tha not all of them are suitable for this trick.
To take only one example, the Linux Kernel isn’t supposed to compile with any kernel but gcc (ie: it has a lot of gcc-only extensions (__asm__(), …)
Perhaps Intel implement some of theses, but I don’t really want to take the risk.
i think icc 7.1 is more favourable than the reviewed icc 7, in regards to performance and debugging ability and ability to link to gcc objects.
> The thing is, I don’t do heavy development, so I am certainly not willing to pay 400 bucks for a compiler. Once the evaluation period ends, you’ll be screwed because of the incompatibility.
Then if you use Linux, you can go and download the “Free Unsupported version” intended for noncommerical purposes.
http://www.intel.com/software/products/compilers/clin/noncom.htm
ICC’s main strength lies in Itanium, and the main reason of icc’s development was to support Itanium’s EPIC architecture. Because of the FUD beiung spread against it claiming “there’s no good compiler for EPIC -> Itanium sucks”.
In this respect, gcc is far behind…
Just a little word, ecc/efc is for the Itanium, not icc/ifc. That said, I hate efc with a passion. I have never been able to use it properly. Now, granted, part of that hatred was due to GNU binutils (ld), but I still don’t like it.
On the other hand, I’ve had pretty good success with ifc on Xeons. Quite a nice compiler. I still think that ifc doesn’t interact with C code as well as Intel seems to believe. Of course, the annoying thing about ifc is that it is continuously behind Red Hat. Remember, IFC 7.1 does not work on RH 9 and even NPTL 8.0 systems (well, without *very* ugly hacks). That is causing more problems for people now than anything.
The requirements are not as harsh as they state in the article. I’ve installed all of the icc-versions since 6.0 on my Debian unstable. It works fine with glibc 2.3.1, but glibc 2.3.0 had a few bugs that made the headers inparsable by compilers that didnt define _GCC (icc 7.2 has “fixed” this by defining it and thus claiming to be gcc).
To use the rpm’s in alien you first has to remove the uninstall-scripts since debian wont accept conflicting files.