Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!ukc!edcastle!spider!raft.spider.co.uk!spiderman!scottm From: scottm@spiderman.spider.co.uk (Scott Mackie) Newsgroups: comp.sys.hp Subject: Re: Switching from Sun to HP: some general questions Message-ID: <1991Apr29.121653.20625@spider.co.uk> Date: 29 Apr 91 12:16:53 GMT References: <7370381@hpfcso.FC.HP.COM> Sender: scottm@spiderman () Reply-To: scottm@spider.co.uk Followup-To: comp.sys.hp Organization: Spider Systems Ltd Lines: 32 Nntp-Posting-Host: spiderman.spider.co.uk In article <7370381@hpfcso.FC.HP.COM>, mjs@hpfcso.FC.HP.COM (Marc Sabatella) writes: |> >The patches that I applied were to some 68XXX assembler in the src dir... I think |> >it was alloca.s. Obviously that doesn't apply to the 800's.... |> > |> >I can dig out the notes I got from HP Support if anyone's interested... |> |> So it's not an "assembler patch" - that would mean there was a problem with the |> assembler. It's a "source patch", in this case meaning the problem is with |> the software. Uhh, yeah.... My fault for sloppy typing... Mind you, anyone who thinks I'd apply a patch to as(1) instead of fixing the source is being a tad silly ;-) |> alloca() and crt0 are not things that "portable" programs should be messing |> with. Doing so merely guarantees your software will not be portable. Software |> that adheres to standards (POSIX especially) should port with no problem. The patches, as I remember (I ask for artistic licence here as it's been about 9 months !), were to the pieces of code *inside* the HP assembler switches in alloca.s. I don't see that affecting future ports to other manufacturers platforms. Scott..... p.s. POSIX and Portability? Shurely Shome Mistake? ;-) -- Spider Systems Limited Net: scottm@spider.co.uk Spider Park, Stanwell Street, Edinburgh YellNet: +44 31 554 9424 #include "Rockin' Good, Peanut!"