🚀 go-pugleaf

esp_05@jhunix.HCF.JHU.EDU (Stdnt 05) writes:
I just downloaded the copy of GNU C from terminator, oh, two weeks
>ago, the same time I downloaded the pml package.  Maybe I should try
>drgsun.

Bammi recently put GCC 1.36 on his server -- say "gcc -v" to find out
what version you're using.

>At any rate Megamax C blew GNU C away in speed and executable size
>(GNU C took twice as long, and the executables were around twice as
>large).  The only problem with it is that it doesn't have stdlib
>functions, although without those I can still improvise.

When you say "executable size" do you mean the size of the PRG file?
That's not a good indication.  There can be any amount of information
in the PRG file besides the program: symbol tables, debugging
information, etc.  If you use -g on the GCC command line, that's your
answer: it generates LOTS of info for the symbolic debugger GDB (and
UN*X's dbx).

The right way to find out executable size is to dump the program's header
and look at the size fields.  The dump will look like this:

	60 1a tt tt tt tt dd dd dd dd bb bb bb bb ...

601a is a magic number.  tttttttt is the text (program) size in bytes.
dddddddd is the data segment size in bytes.  bbbbbbbb is BSS. Compare
the SUM of text + data, because GCC might be putting strings in the
text segment, while Megamax might put them in the data segment. Also
make sure they're both talking about the same things: use -mshort for
your comparison (even if the program doesn't work that way) if Megamax
has 16-bit INTs.

Of course, MegaMax C has *8* bit shorts, and some required keyword
concerning modules or overlays or something, so I have no respect for
it at all...

============================================
Opinions expressed above do not necessarily	-- Allan Pratt, Atari Corp.
reflect those of Atari Corp. or anyone else.	  ...ames!atari!apratt