HP3000-L Archives

April 1995, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bruce Toback <[log in to unmask]>
Reply To:
Bruce Toback <[log in to unmask]>
Date:
Mon, 17 Apr 1995 08:12:13 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
Daniel Kosack writes:
>  I've never really used C/iX, but is there a compiler option to compile
>for the Classic MPE/V architecture?  If so, would it be possible to
>compile a version of GCC and G++ for MPE/V?  A C/C++ compiler for MPE/V
>could come in quite handy.
 
There is a commercial C compiler available for MPE/V, and another that
could be freeware if we can solve a couple of legal problems. Unfortunately,
GCC/G++ won't compile for MPE V without a LOT of work. MPE/V is very much
a 16-bit architecture, and GCC/G++ assume the availability of more than
32k of data. It would be possible to change them, but I don't know that
you'll find anyone willing to do it.
 
>  I would trust GCC and G++ probably more than C/iX.  Yes, it isn't
>supported by one company, but it is developed by many programmers all
>over the world, from many various organizations.  GCC/G++ would add such
>a variety of software compatibility to the MPE platform, if successfully
>ported.  Porting code from UNIX to MPE would certainly be easier.
 
C/iX is a good, solid compiler, and it knows about a lot of 3000-isms
that GCC/G++ don't, and probably won't for a while. The biggest
problem is the lack of the Modcal calling sequence for variable-length
and omitted parameters in parameter lists.
 
-- Bruce Toback
[log in to unmask]

ATOM RSS1 RSS2