🚀 go-pugleaf

In article <296@adiron.UUCP> tro@adiron.UUCP (Tom Olin) writes:
>I am attempting to use the DECUS C compiler on RT-11 V4.  The
>compile-time environment that I have consists of CC.SAV, AS.SAV, and
>CLIB.OBJ.  Other than a few source files (GREP.C, ECHO.C, etc.), that's
>it.  No documentation of any sort.
>
>When I run CC, I can get it's usage line, but when I attempt to compile
>anything, I get the message "?MON-F-No dev[ice] nnnnnn", where the nnnnnn
>varies, depending on exactly how I enter the command line.  The devices
>I have on my system are DY0 (SY), DY1 (DK), LS (LP), NL, and TT.
>
>Questions:
>
>	(1) Exactly what is CC complaining about?  What must I do to
>	get it to work?
>
i
CC isn't complaining, as such. RMON is. There is, in fact, a bug in the
CC compiler that occurs when you try to use the compiler with the
pre-processing phase turned off. I have encountered the problem also
and have spoken to Martin Minnow about (the guy who wrote it). If you
attempt to use the compiler with the /m switch, this problem will
occur. I have found the following command line nearly always works,
though:

	.R CC
	CC> file

Replace, of course, 'file' with the filename of the source your compiling.
Occasionaly (especially on large sources/small disks) you will run into
the problem of space allocation for the intermediate files. This may
require you to specifically allocate the space for these files:

	.R CC
	CC> file.s,file.tmp[nnn],file.tm1[nnn]=file

"nnn" has to be played with, but often something about 5 times the source
file works. 


>	(2) What is the meaning of the various command line switches?
>

	/a - chain to AS upon completing the compile
	/d - pass all single precision floats to functions as double precision
	/e - generate in-line code for multiply, divide, xor for EIS
	     machines
	/f - pass all single precision lfoats as single precision
	/l - write internal code tress as comments to .S file
	/m - disable macro pre-processor (broken)
	/n - generate calls for multiply, divide, xor, etc.
	/p - add profiling code
	/r - define symbol "rsts"
	/w - supress "variable defined but unused" compiler warnings

There are others, but are used for debugging the compiler. Don't use them.

>	(3) If I can get CC working, I assume I run its output through
>	AS.  Am I correct?  Is there anything else I should know about
>	the compiler, such as special LINK options?
>

There is one other file needed, that is SUPORT.OBJ. When you link, your
command should look like:

	.LINK/BOTTOM:2000 file,C:CLIB,C:SUPORT

the /BOTTOM switch allocates sufficient stack space for the runnable
image. If you need more, than increase the value.


>If anybody has some documentation which will answer these questions, I
>would like to make arrangements to receive it.
>

For anyone who has this dilemna, reply to me and I will get you a copy
(via floppy).


>Please send responses to ...duke!adiron!tro.