Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!utfyzx!oscvax!rico
From: rico@oscvax.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: replacement for frags
Message-ID: <482@oscvax.UUCP>
Date: Wed, 15-Apr-87 09:13:35 EST
Article-I.D.: oscvax.482
Posted: Wed Apr 15 09:13:35 1987
Date-Received: Thu, 16-Apr-87 01:49:21 EST
References: <3148@jade.BERKELEY.EDU>
Reply-To: rico@oscvax.UUCP (Rico Mariani)
Organization: Ontario Science Centre, Toronto
Lines: 25
Summary: 

In article <3148@jade.BERKELEY.EDU> mwm@violet.berkeley.edu(Mike (My watch has windows) Meyer) writes:
> [Edited:  a whole bunch of source ]
>
>/*
> * To cut down on memory useage, we provide a stub for a routine pulled
> * in by the default startup code in _main. This code cleans up
> * dynamically allocated memory, which we don't need. So we flush the code
> * here. By making this a smallcode, smalldata program, turning off stack 
> * checking (nothing recursive, and only three routines, so who needs it?),
> * and adding this, I've reduced the size of frags to 1644 bytes. Since the
> * original frags is 1964 bytes long, I'm happy. Just out of curiosity, I'd
> * like to know how large a binary Manx 3.4 produces.
> */
>void
>MemCleanup() {}

Manx 3.4, using just the +L option (force 32 bit integers) compiled the
code just fine (once I removed the ANSI-style argument type declarations)
and produced a 796 byte binary.

	-Rico
-- 
[NSA food: terrorist, cryptography, DES, drugs, CIA, secret, decode]
[CSIS food: supermailbox, tuna, fiberglass coffins, Mirabel, microfiche]
[Cat food: Nine Lives, Cat Chow, Meow Mix, Crave]