On Tue, Nov 08, 2005 at 10:33:26AM -0500, Tom Cada wrote:
> I think there may be some problems with the use of another compiler.

Sure! ;-)

> First of all, what compiler does say the KDE group use? If a problem occurs 
> when using the Intel compiler but doesn't show up with GCC, and KDE uses the 
> GCC compiler, then who is responsible for correcting it? I'm sure that KDE 
> would say "Take care of it yourself".

Building a distribution yourself without the knowledge how to fix bugs is
stupid anyway in my opinion.

> Secondly, are there any conflicts in the combining of routines that may have 
> been created using different compilers? That is, a huge system such as KDE 
> has many subroutines. Subroutines compiled with one compiler may not play 
> nice with subroutines compiled with another compiler. These bugs are not 
> simple to find, and may occur in very special and unusual circumstances.

The Intel compiler is ABI compatible to gcc.  Otherwise he couldn't use
libstdc++ from gcc anyway.  Sure there is still the risk that something breaks
due to this problem but then this is a bug in the compiler and Intel would
sure be happy about a decent bug report.

> Thirdly, for the user that wants to use a program available in source only, 
> do 
> they have to install the compiler based upon the distribution? Would you 
> start to include the Intel compiler as part of the repositories?

That would be illegal.  But you can freely mix both compilers.

> Has anyone developed a list of good programming techniques to enhance the 
> speed of program? Perhaps a route to go would be a project to review 
> individual programs to see if they have any coding that could be improved for 
> speed based upon those techniques. The list could be set to include only high 
> resource usage programs such as image viewers and editors.

Cleaning up and tuning the code of applications is definitely the more
promissing way than just blindly replacing the compiler.

Robert

-- 
Robert Schiele                  Tel.: +49-621-181-2214
Dipl.-Wirtsch.informatiker      mailto:[EMAIL PROTECTED]

Attachment: pgpGwrraBRTaz.pgp
Description: PGP signature

Reply via email to