Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!watcgl!kdmoen
From: kdmoen@watcgl.UUCP
Newsgroups: comp.sys.mac
Subject: Re: What is wrong with the Sumacc C compiler
Message-ID: <2284@watcgl.waterloo.edu>
Date: Sun, 8-Nov-87 05:54:56 EST
Article-I.D.: watcgl.2284
Posted: Sun Nov  8 05:54:56 1987
Date-Received: Sun, 8-Nov-87 18:49:07 EST
References: <7486@dartvax.UUCP> <7508@dartvax.UUCP> <21522@ucbvax.BERKELEY.EDU> <9431@ut-sally.UUCP>
Reply-To: kdmoen@watcgl.waterloo.edu (Doug Moen)
Organization: U. of Waterloo, Ontario
Lines: 25
Keywords: C compiler gripe

brian@ut-sally.UUCP (Brian H. Powell) writes:
)	Segmentation, as we all know, is a means of getting around the problem
)that the mac has with segments of code that are larger than 32K.  This meant
)that you couldn't write a program in SUMacC that was larger than 32K.

I have been developing/maintaining a very large Sumacc program since Sumacc
was first released.  (Before that, we used the Lisa Workshop & Lisa Pascal).
When we stopped using Sumacc earlier this year it was >100K, and it ran fine.

)     For SUMacC to be competitive, it would have to generate
)position-independent code, and it would have to provide segmentation.  It's
)code generation is among the best (if not the best) considering it does a
)reasonably good job at optimization.
)
)Brian H. Powell

When I translated the program to MPW C, the code size dropped to 2/3 of its
size under Sumacc.  This is despite the fact that I junked the compiler
supplied with Sumacc and replaced it with a slightly better version of the
MIT 68K C compiler, which I then proceeded to hack to improve code quality.
-- 
Doug Moen
University of Waterloo Computer Graphics Lab
UUCP:     {ihnp4,watmath}!watcgl!kdmoen
INTERNET: kdmoen@cgl.waterloo.edu