Newsgroups: comp.lang.apl
Path: watmath!watserv2.uwaterloo.ca!torn!cs.utexas.edu!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!sdd.hp.com!elroy.jpl.nasa.gov!jato!csi!sam
From: sam@csi.jpl.nasa.gov (Sam Sirlin)
Subject: Re: Porting J51a to HP-UX, HP series 700 machines
Message-ID: <1992Nov4.191552.13176@csi.jpl.nasa.gov>
Originator: sam@kalessin
Sender: usenet@csi.jpl.nasa.gov (Network Noise Transfer Service)
Nntp-Posting-Host: kalessin
Organization: Jet Propulsion Laboratory, Pasadena, CA
References: <Bw9nFy.E0s@NCoast.ORG> <1992Oct21.231634.17756@yrloc.ipsa.reuter.COM> <1c8gruINN7lc@nestroy.wu-wien.ac.at>
Date: Wed, 4 Nov 1992 19:15:52 GMT
Lines: 34


In article <1c8gruINN7lc@nestroy.wu-wien.ac.at>, mitloehn@exaib.wu-wien.ac.at (Johann Mitloehner) writes:
|> A few technical questions (sorry!):
|> 
|> Has anyone ported J51a to HP 9000/700 machines running HP-UX?

Note that J 6 is out now.

|> We had no trouble to compile the source for the series 300 machines,
|> but for the 700s (which are much faster), we have the following problem:
|> J seems to work until I enter a vector of numbers (instead of scalars);
|> then program coredumps. Any hints would be greatly appreciated!

You should be more specific. Especially as to what compiler and
options you're using, and what expression causes the problem so the
rest of us can try it. After all there might just still be bugs
lurking around somewhere. One thing I've noticed is that J won't run
under gcc 2.2 on a risc machine (sun sparc), as riscs require various
memory alignment that J doesn't do (is the hp 700 risc?). The symptoms
I see when this happens sound like what you get (bus error). I traced
it to memory alignment problems using xdbx.  For me, the fix was to
keep gcc 2.1 around and use that for J.  Different c compilers on
different machines have different alignment requirements. After all, c
is a low level language and hence can't be completely standard (;-).

|> BTW: What does the library cfix contain? It's not a standard C library,
|> is it? 

I junked that link. Probably machine specific. You don't need it.

-- 
Sam Sirlin
Jet Propulsion Laboratory         sam@kalessin.jpl.nasa.gov

