From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: (slightly OT) DJGPP Allegro is faster then MingW32 Allegro? Date: 29 Jan 2001 13:46:58 GMT Organization: Aachen University of Technology (RWTH) Lines: 28 Message-ID: <953s8i$nsc$1@nets3.rz.RWTH-Aachen.DE> References: <951vr9$9bf$1 AT nnrp1 DOT deja DOT com> <953o1i$k6g$1 AT nnrp1 DOT deja DOT com> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 980776018 24460 137.226.32.75 (29 Jan 2001 13:46:58 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 29 Jan 2001 13:46:58 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com [Could you all please reduce quoted content to the part you're actually referring to? Thanks.] Tom St Denis wrote: >> On Sun, 28 Jan 2001 20:35:53 GMT, Tom St Denis >> wrote: [...] >> >I get 850,000 hlines per sec with DJGPP and 400,000 with MingW. >> > >> >Any clues to why it's slower? > Well it gets wierder. My 3d library+test runs at the same fps in djgpp as > ming. It's only tests/test.exe that differs. That latter one is not a surprise at all, IMHO. Unless yours is an extremely strange 3D library, it's almost certainly going to be limited by other factors than execution speed of single API calls. Or if it's limited by API call processing, then the API call it bottlenecks is hardly ever going to be hline(). 3D textured and lighted polygons exercise other functions much more heavily. Actually, I'd be surprised if a 3D library ever executed a single call of the hline() method. Horizontal lines simply don't happen often enough, in 3D, to make it worthwile checking for this special case and calling the specialized hline() for them. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.