delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1992/10/06/11:58:43

From: Eric Backus <ericb AT lsid DOT hp DOT com>
Subject: Re: GCC16: Any reason not to use it?
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Date: Tue, 6 Oct 92 8:40:48 PDT
Mailer: Elm [revision: 66.25]

> >My understanding is that GCC is merely an executive, that calls CPP,
> >CC1, etc to do the actual work; i.e., GCC itself does not do any 32 bit
> >operations.  This being so, is there any reason to use the 32 bit
> >version of GCC, given that it will be slower than the 16 bit version.
> 
> Purity?  Pride?  Memory usage?  Maybe there isn't any good reason,
> except that it gets built by gcc-2.2.2 so I ship it.  Gcc16 requires
> some funky rewriting to get it to run under Turbo C.
> 
> On my machine it *is* the default.

If it doesn't use go32, does that mean it doesn't understand long
command lines via "@filename" or via the GNUish environment variable
method?  At least for me, long command lines are worth more than a
faster compile.
--
				Eric Backus
				ericb%hplsla AT hplabs DOT hp DOT com
				(206) 335-2495

- Raw text -


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