[Nasm-bugs] [Bug 3392380] lack of support for PE-COFF symbol type

noreply-nasm at gorcunov.org noreply-nasm at gorcunov.org
Mon Feb 25 09:23:02 PST 2019


andreas.ringlstetter at gmail.com changed:

           What    |Removed                     |Added
                 CC|                            |andreas.ringlstetter at gmail.
                   |                            |com

--- Comment #2 from andreas.ringlstetter at gmail.com ---
Lack of the type field also triggers a bug with Microsoft's toolchain.

The librarian treats symbols with mismatched type field as incompatible. If an
object in the scope of a library declares an import by declaration of a
function, and an object created by NASM the implementation, then the librarian
keeps both symbols. The first one remains unresolved.

The linker in contrast ignores the type field, but it will never attempt to
resolve a unresolved dependency using a symbol from the same input. (Unless the
linker gets confused, but I have no idea how to induce that state.)

So in the current state it is not possible to assemble a library with a
self-contained C/C++ wrapper around a function compiled for win32 / win64
target with NASM.

You are receiving this mail because:
You are watching all bug changes.
You are on the CC list for the bug.

More information about the Nasm-bugs mailing list