[Info-vax] IA64 assembler file in shared image - ILINK-W-NOTPMTIDX

[John E. Malmberg]

On 3/21/2015 3:17 AM, hb wrote:
> On 03/21/2015 05:54 AM, Michael Moroney wrote:
>> "John E. Malmberg" <wb8tyw at qsl.network> writes:
> ...
>>> %ILINK-W-NOTPMTIDX,  section (index 0x00000000) encountered when trying
>>> to index PMT
>>>          module: UNIX
>>>          file: LCL_ROOT:[libffi.ia64-dec-vms.libs]libffi.a;1
>>> %ILINK-W-NOTPMTIDX,  section (index 0x00000000) encountered when trying
>>> to index PMT
>>>          module: UNIX
>>>          file: LCL_ROOT:[libffi.ia64-dec-vms.libs]libffi.a;1
> ...
>> $ help/message NOTPMTIDX
>>
>>   NOTPMTIDX,  'symbol-type' symbol (index 0x'hexadecimal-number')
>>               encountered when trying to index PMT
>>          module: 'module-name'
>>          file: 'file-name'
>>
>>    Facility:     ILINK, OpenVMS I64 Linker Utility
>>
>>    Explanation:  The section index is not identifiable as a valid
>> section index
>>                  by the linker.
>
> Symbol-type is not shown, here. So it is likely a local symbol causing
> this. Check with analyze/object/section=symtab for (local) symbols which
> have a shndx of 0 (analyze labels this field with "Bound to section:").
> For a local symbol this would mean an undefined one, which the linker
> has no chance to resolve (from where???). So itis a problem in the
> object which the linker reports.

SYMBOL 23.
"OTS$MOVE" bound to section 0. (SHDR$K_SHN_UNDEF) symtab$w_st_shndx

SYMBOL 24.
"ffi_closure_unix_inner"  Bound to section  0.
       (SHDR$K_SHN_UNDEF)           symtab$w_st_shndx

> Without looking at the object, this can be either a problem in the IA64
> assembler (Have your system manager contact...) or in the sources.

The Eisner web server was down last night, so I could not post a link.

http://eisner.encompasserve.org/~malmberg/GNV/UNIX_MAR_IA64.TXT

This is the libffi itanium code with patches from Philippe Vouters.

Even though there are the two warnings.  The code somewhat works, at 
least what I have been able to test.

S_Float is not correctly implemented and complex support is missing.

I have not tested the closure functions at all.

Regards,
-John