From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,7b18a1fb8616a59d
X-Google-Attributes: gid103376,public
From: kilgallen@eisner.decus.org (Larry Kilgallen)
Subject: Re: Assembly and Ada
Date: 1997/04/10
Message-ID: <1997Apr10.133822.1@eisner>#1/1
X-Deja-AN: 232123937
X-Nntp-Posting-Host: eisner.decus.org
References: <334AF688.1573@moon.pr.erau.edu>
X-Nntp-Posting-User: KILGALLEN
X-Trace: 860693917/12235
Organization: LJK Software
Newsgroups: comp.lang.ada
Date: 1997-04-10T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <334AF688.1573@moon.pr.erau.edu>, stephen king <kingst@moon.pr.erau.edu> writes:
> How do I interface assembly commands with Ada?

Presuming you meant assembly "instructions"...

Since you did not specify, I guess I get to choose the hardware and
operating system; I choose Alpha VMS.

Decide which you want to use --- Macro-32 or Macro-64, and build
your module with an external entrypoint.  Use the IMPORT_FUNCTION
or IMPORT_PROCEDURE pragma to make it known to your DEC Ada program.

There is also an Alpha VMS version of GNAT Ada coming, and Robert Dewar
can indicate whether ACT has current plans for inlining assembler code.

Larry Kilgallen