Date: Mon, 9 Jun 1997 14:19:48 +0200 (MDT) Message-Id: <3.0.16.19970609194139.3567dcf6@hem1.passagen.se> To: Jan Hubicka From: Peter Palotas Subject: Re: Speed of DJGPP? Cc: djgpp AT delorie DOT com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Precedence: bulk At 13.28 1997-06-09 +0200, you wrote: > On Thu, 5 Jun 1997, Peter Palotas wrote: >> Okay, then I misinterpreted what the guy wrote. This makes more sense. >> Although, I presume DJGPP makes faster code than BC!? Although, it produces >> about the same code as Watcom from what I have understood, so the question >not exactly same. In more complex tests(like floating point mandelbot loop) >is gcc still twice faster then wc. Well, that is not completely true. I wrote a madelbrot program for my math class just about two weeks ago, and a friend of mine had a friend of his write another mandelbrot program for him, I wrote mine in DJGPP (ofcourse) and he wrote his in Watcom. There was a small diffrence in speed, his was a little bit faster on a Pentium, and we used the exact same algorithm in the main loops. But as far as I know, DJGPP does not optimize code for Pentiums which Watcom does so that might explain it. But then I wonder how did they do it with quake? I mean Quake must have Pentium optimizations, did they write thos in inline ASM or something or what? >> is, why does it have to be slower? >I personally think that it is sloweb because compiler is more unix oriented- >has more separated phases. As far as I know watcomm has just one program >that does whole compilation and outputs in object..gcc has separaed >assembler,compiler etc...so it forces some temporary files. >I am also not sure if watcomm uses something like RTL What's RTL? Well, yeah, DJGPP uses more temp-files, I'm just wondering why not try and solve that problem by integrating the diffrent compilers, preprocessors and assemblers a bit more, so that they don't have to use temporary files. ------- Peter Palotas alias Blizzar -- blizzar AT hem1 DOT passagen DOT se --------- ********************************************************************* * A brief description of DJGPP: * * Never before has so few people done so much for so many... DJGPP! * *********************************************************************