From: adt AT netcom DOT com (Tony Tribelli) Newsgroups: comp.lang.c++,comp.os.msdos.djgpp,rec.games.programmer Subject: Re: The numer 1 compiler, DJGPP or MSVC Here's a good rating comparision Date: Mon, 08 Sep 1997 21:05:02 -0700 Organization: Delta Internet Services, Inc. Lines: 40 Message-ID: References: <3412BD25 DOT 1F30 AT mho DOT net> <5uuqci$15l AT sjx-ixn5 DOT ix DOT netcom DOT com> <5v1nfs$g9b$2 AT news DOT sendit DOT nodak DOT edu> NNTP-Posting-Host: 204.254.69.38 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk adalee AT sendit DOT sendit DOT nodak DOT edu (Adam W Lee) wrote: > : Possibly true with respect to the ancient 16-bit MSVC++ 1.0 that the > : original poster mentioned and your 486 system. But if we consider more > : recent 32-bit versions, 4.2 and 5.0, targetting Pentium systems, then gcc > : falls way behind. It also trails Watcom and Borland with Intel's backend > : optimizer. > > PGCC isn't too bad, though. It was several months ago, but one of about 6 programs I ran through it actually got slower. > : For DOS targets professionals used to choose Watcom, for Win32 targets they > : usually choose Visual C++. > > I know a lot of people doing Win32 stuff in Watcom, though since you can > so easily compile for both. > > : gcc is a little flaky with C++, exception handling is the most notorious > : example. Also AT&T assembly syntax is a problem, not an advantage. > > OK, I'll give you that GCC's C++ isn't picture-perfect, but that's doding > the fact that it supports 5 times as many languages as MSVC. > > Also, you may be having problems switching from Intel to AT&T, but that > doesn't make it a problem. Some people can't grasp C++ but that doesn't > make a compiler's support of it a problem. The problem is that the vast amount of resources and tools available are in Intel format not AT&T. AT&T syntax users often have to convert and type, Intel syntax users often cut-and-paste tested working code. Now let's discuss some of the profiling and analysis tools around that help optimize code for Pentium UV pipes, Intel syntax. How about In-Circuit emulators, Intel syntax. Tony ------------------ Tony Tribelli adtribelli AT acm DOT org