Re: Linking Ada with large Assembler libs?

["Rolf" <rolf.ebert_nospam_@gmx.net>]

On Feb 21, 10:29 pm, "freejack" <freej...@tds.net> wrote:
> The Machine Code Insertions sections of the relevant reference manuals
> have been informative.
>
> However, I'm linking my Ada code with pre-existing libs written in
> Assembler. The GNAT manuals are a little sketchy on how to do this
> properly. I'm using NASM and FASM Assembler code. Most of the
> Assembler code deals primarily with I/O. I'm using Pragma No_Run_Time
> and writing my own Binder files, with a good bit of success.
> It's not such a big problem, as I can do it by fiddling with the
> linker and manipulating the object code. But the result is messy and
> error prone.
>
> What are the best methods you guys have come up with for doing this
> sort of manipulation?

I either used inline assembly code in the body of an Ada procedure
(preferred) or pragma Import (Convention => C, ...) when programming
the AVR microprocessors.  In the latter case you have to follow
exactly gcc's parameter passing mechanism in the assembly code (e.g.
for AVR the first arg is in r24/r25, the second arg in r26/r27, etc.).

In the recent AVR-Ada releases we don't use assembly anymore;
everything is Ada now with almost identical asm code.  I'm considering
to use Asm code for bin->ascii conversions, though.

In the beginning I also used my own hand written binder file, now I
have a patch to gcc in order to generate a binder file that fits my
needs.

Have a look at pragma Linker_Options. You can use it for simple things
like including the object file for your assembler code, but also for
using special linker scripts.

HTH

    Rolf