delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1992/07/10/07:59:12

Date: Fri, 10 Jul 92 13:06:09 +0100
From: buers AT dg1 DOT chemie DOT uni-konstanz DOT de (Dieter Buerssner)
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Cc: dj AT ctron DOT com
Subject: go32 1.07 is much faster when compiled with TOPLINEINFO=1

First of all, thanks DJ for djgpp, which I'm very much enjoying; it's great.

But now to my problem: After installing djgpp1.07 and recompiling my 
programs, I recognized that compiling was much slower than with 
djgpp1.06. Then I tried gcc.exe from contrib/gcc16. On one machine
(386SX, 16 MHZ, 3 MB RAM, 1 MB XMS, rest cache) I got the error
message "out of conventional memory". What does it mean?. There was 
enough swap place left on the HD. On another machine (486, 33 MHZ, 4 MB RAM,
1.6 MB XMS/EMS, rest cache), I got " ... segmentation violation ... ".
This was reproducible, and only happened with the 16 bit gcc.exe.
It seemed, that there was a lot of swapping going on, so
I recompiled go32.exe with TOPLINEINFO defined as 1. The errors went
away on both machines and compiling was approximately by a factor of 2
faster. I thought, that go32.exe in djdev107.zip might be out of date
and recompiled with TOPLINEINFO=0 => compiling was slower again.
I guess, that there must be a inconsistency in the sources 
of go32 when TOPLINEINFO is defined as 0. Can somebody explain
this or does somebody know a work around.

       Thanks
              Dieter

Dieter Buerssner  (B\"ur\ss{}ner) -- buers AT dg1 DOT chemie DOT uni-konstanz DOT de
Universitaet Konstanz -- Fakultaet Chemie -- Postfach 5560 
7750 Konstanz  -- Germany -- +49-7531-882021

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019