🚀 go-pugleaf

In article <1830@ibmpa.UUCP> brunner@ibmsupt.UUCP () writes:
>
>
>The current (2.1s) hc compiler is now available as a compressed
>tar file on ibmsupt. This version replaces all earlier versions
>of the hc compiler and corrects all reported problems with the
>compiler, including some reported as problems with the dbx.
>The compressed tar image contains the first and second pass of
>the hc compiler, /usr/lib/hc?com. The driver, /bin/hc is unchanged
>and is not included.
>

If someone at a Internet site has picked this up, could you
contact me and make arrangments for us to get a copy? We can 
show all the appropriate licenses and such, we just don't have 
dial out UUCP access right now. 


And, on a slightly related note, is anyone using the if_un.c 
posted as V1.12 on a 6152 with more then 1 ethernet card. 
The driver seems to have fixed the earlier crashes we were having,
as long as the machine is running a kernal configured for 1 ethernet
card. If we try to boot a kernal with >1 ethernet card support, it
crashes at the probe. We realy want to use this 6152 as a gateway! 


Thanks for any help or suggestions,
Eric Johnson
U of Florida
<esj@ufl.edu>

Has anyone compiled the X11R3 Xibm code with the new compiler?
(Jeff W. aka: Skippy The WH -- what results have you had?)

I had some problems with vgaData.c and mpelData.c.
-- make output --
-- for mpelData.o --
rm -f mpelData.o
hc -c -g -L/usr/cs/lib -I. -I../BSDrt -I../../mfb -I../ppc 
    -I../../../include -I../../../.././X11 -I../common 
    -I../../../../extensions/include -DUNIXCPP -DNOSTDHDRS -DHCVERSION=21018 
    -DBSDrt -DRTIO  mpelData.c
E "mpelData.c",L226/C2:	mpelSetColor
|    Type "void(unsigned long number,unsigned short red,unsigned short green,
     unsigned short blue,VisualPtr pVisual)" is not assignment compatible with 
     type "void(*)()".
1 user error   No warnings   
*** Exit 8

Hc1.4 has no problems producing object code from these C files.

Also, note that when I check out the HCVERSION using the method suggested
in Rt.macros, the version of hc2.1 is reported as 'hc2.1r' NOT 'hc2.1s'
as stated by ACIS.  ???????

The new compiler also finds alot of "...Expression has no side effects",
and "...Result of comparison never varies" comments when compiling the 
Magic program from the Berkeley VLSI tools.  We usually jump ship and switch
to hc1.4 when we see these kinds of errors.

					-Kris Olander
	(just in case .sig)		 Sys. Eng.
	(doesn't get appended)		 Project NORTHSTAR

# Kris Olander ---- ---- arpa: kriso@northstar.dartmouth.edu #
# ---------------------------------------------------------- #
# System Eng. Project NORTHSTAR                              #
# Thayer School of Eng., Dartmouth College                   #

In article <20803@uflorida.cis.ufl.EDU> esj@bikini.cis.ufl.edu (Eric S. Johnson) writes:
>In article <1830@ibmpa.UUCP> brunner@ibmsupt.UUCP () writes:
>> (hc 2.1s' virtues and availability, deleted)

Let me know if you can't get the 2.1s version via channels, we're
phoning all the known/official IBM/4.3 contacts, and it will help
us in fixing the support system's problems.

>And, on a slightly related note, is anyone using the if_un.c 
>posted as V1.12 on a 6152 with more then 1 ethernet card. 
>The driver seems to have fixed the earlier crashes we were having,
>as long as the machine is running a kernal configured for 1 ethernet
>card. If we try to boot a kernal with >1 ethernet card support, it
>crashes at the probe. We realy want to use this 6152 as a gateway! 

We know about the 2 card crashes -- and we are working on it. We did
not think to test the two-ethernet card configuration, to our chagrin!


Eric Brunner, IBM AWD Palo Alto
inet: brunner@monet.berkeley.edu or brunner%ibmsupt@uunet.uu.net
uucp: uunet!ibmsupt!brunner		(415) 855-4486

The version installed on ibmsupt was the 2.1r version. This version was
installed in error, and has been replaced with the correct 2.1s version.
Please copy the correct version and accept my appologies for the error.

When the uncompressed, the tar image contains the two passes only (the
driver, /usr/lib/hccom, is unmodified and so not included), with the
sizes, dates and names shown below. Install these in /usr/lib as hc1com
and hc2com, either using move to rename the files, or using symbolic
links, e.g., ln -s /usr/lib/2.1hc1com /usr/lib/hc1com, similarly for the
second pass, hc2com.

-rwxr-xr-x  1 brunner  wheel      321536 Aug  8 18:33 2.1shc1com*
-rwxr-xr-x  1 brunner  wheel      342016 Aug  8 18:33 2.1shc2com*

To determine the version of the hc compiler, pass the -v switch (verbose)
to the compiler. The version will be printed to stdout as shown in the
example below. hctest.c is a minimal "main(){}" source file.

% cc -v hctest.c
/lib/cpp -D__STDC__ -D__HIGHC__ hctest.c /tmp/pp.002251
/usr/lib/hc1com /tmp/pp.002251 -efile @E -silent -on CHAR_DEFAULT_UNSIGNED -off DOUBLE_MATH_ONLY -on DOUBLE_RETURN -on LONG_ENUMS -off PCC -on PCC_MSGS -ofile /tmp/IL1002251 -vfile /tmp/var002251 -machine rtfl -define ibm032 1 -pro hc.pro -copyr -dir /usr/include
MetaWare High C Compiler R2.1s 
(c) Copyright 1987-89, MetaWare Incorporated
/usr/lib/hc2com -i /tmp/IL1002251 -V /tmp/var002251 -s hctest.c -S /tmp/S002251 -e -T /tmp/HC2002251
/bin/as -o hctest.o -V /tmp/S002251
/bin/ld -X /lib/crt0.o hctest.o -lc

If you have problems getting High C version 2.1s, please let me know via mail
or phone.

Eric Brunner, IBM AWD Palo Alto
inet: brunner@monet.berkeley.edu or brunner%ibmsupt@uunet.uu.net
uucp: uunet!ibmsupt!brunner		(415) 855-4486

In article <15356@dartvax.Dartmouth.EDU> kriso@northstar5.dartmouth.edu (Kris Olander) writes:
>
>The new compiler also finds alot of "...Expression has no side effects",
>and "...Result of comparison never varies" comments when compiling the 
>Magic program from the Berkeley VLSI tools.  We usually jump ship and switch
>to hc1.4 when we see these kinds of errors.
>
Kris, did you look at the source code that caused those warnings? 
We have found many of errors in BSD source with the help of the hc
warnings.  "result of comparison never varies" usually occurs on an if
statement like
		if (c<0) ...
where c has an unsigned type.  This is usually a porting problem, coming
from a default-signed-char environment. 

A statement like
		x+0;
will cause the "expression has no side-effects" warning.  Maybe someone
typed '+' where they meant '='.  Maybe they meant to declare x as volatile.
Or maybe it's deliberate -- but worth checking out, no?  

If you don't like to be warned, well, that's what -w is for.

Speaking of porting problems, if you suspect that an assumption of chars
being signed is causing trouble, try recompiling with
	-Hoff=char_default_unsigned .  "plain" chars will be signed and
you can see if the problem goes away.
Disclaimer: Don't blame my employer, blame:
Larry Breed			(415) 855-4460
uucp: uunet!ibmsupt!lmb		inet: ibmsupt!lmb@uunet.uu.net