delorie.com/archives/browse.cgi | search |
From: | "Daniel Urquhart" <urquhartd AT jlcrowe DOT org> |
Newsgroups: | comp.os.msdos.djgpp |
References: | <39AE1D927549D111A88F00A0C94B9C7D628ECB AT RJ01MAI01> |
Subject: | Re: performance |
Lines: | 14 |
X-Newsreader: | Microsoft Outlook Express 4.72.3155.0 |
X-MimeOLE: | Produced By Microsoft MimeOLE V4.72.3155.0 |
Message-ID: | <J_rs2.41$am3.436396@news.bctel.net> |
Date: | Fri, 29 Jan 1999 15:38:43 -0800 |
NNTP-Posting-Host: | 209.52.196.53 |
X-Complaints-To: | news AT bctel DOT net |
X-Trace: | news.bctel.net 917654569 209.52.196.53 (Fri, 29 Jan 1999 16:02:49 PDT) |
NNTP-Posting-Date: | Fri, 29 Jan 1999 16:02:49 PDT |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
>> I am testing gcc to work instead of Borland C 3.1 but programs are much >> slower. [snip] >> I don't understand. Anybody can explain? >> >I'm troubled too, but I think that the diference in access speed is that the >DJGPP have to switch to real mode to call DOS funcs and it makes your >program slower. Have you tried make your program disk buffer greater. >Remember, DJGPP can access much more than 64KB per selector. > That's probably right. Because recently ported a program from Boarland and it ran much faster. I't does allmost not disk access though.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |