delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/09/10/03:07:35

Date: Thu, 10 Sep 1998 10:01:34 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Rylan <rylan AT inbtekom DOT co DOT za>
cc: djgpp AT delorie DOT com
Subject: Re: PGCC
In-Reply-To: <6t3fta$ieu$4@news2.saix.net>
Message-ID: <Pine.A32.3.91.980910095940.59746B@ieva01.lanet.lv>
MIME-Version: 1.0


On Tue, 8 Sep 1998, Rylan wrote:

> Hi,
> 
> Small unofficial survey: how many people here use PGCC? I tried it a while
> ago and some of one of my stdlib functions (i used my old GCC compiled libc
> with the PGCC GCC compile) did not work right (clrscr()) - My question - if
> this does not work what else does PGCC affect? I took a look at the PGCC
> page, but I want an independant opinion - should I get it and how much of a
> real improvement does it offer? I tried it with a PGCC recompiled Allegro
> lib, and I did not see much of a marked acceleration - or did I just
> probably test it incorrectly / insuffieciently to notice them?
> 
> Can I fix problems (such as with clrscr()) by using a PGCC compiled libc
> with a PGCC GCC instead of GCC libc with PGCC GCC? ClrScr() still cleared
> the screen, but left the top line of text onscreen when I called it from
> PGCC compiled programs.
> 

I tried to build pgcc-1.1a for DJGPP but libstdcxx.a compiled with options
-mpentium -O6 failed many tests in libio and libstdc++. As the result
I returned to egcs-1.1a where I didn't met similar problems.

Andris 

- Raw text -


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