Problem with --js-library, dynamic linking and function in dynamic library

[Stuonts]

We have a project that needs dynamic linking and may use Javascript functions in dynamic libraries
In case if function from JS library is used in dynamic library, it gives error
"Uncaught (in promise) RuntimeError: Aborted(Assertion failed: Missing signature argument to addFunction:"
Generated dynamic library contains '�GOT.func�testJS'
Generated javascript traverses GOT dictionary in reportUndefinedSymbols and tries to use .sig (which is absent)

Seems that either testJS function shouldn't be marked as GOT.func in .wasm or .sig should generated in JS for testJS
Also, some build flags can cause the issue. Please advice.

Emscripten version: 3.1.8
Attached sample (build for Windows in bat, 'set EMSDK_DIR=F:.emsdk\upstream\emscripten' should be replaced in build.bat
sig.zip

[sbc100]

In order to JS functions to be address taken you need to have test_JS__sig: 'v' to you library JS file. The signature (in this case 'v') is a sequence of characters representing the first the return code then that arguments. So vi would a void function that takes a single int.

[Stuonts]

so, Emscripten should generate .sig in Javascript file? Is it a bug of Emscripten?

[sbc100]

No, you (currently) need to explicitly write the __sig into your library file. Kind of like we do in the core libraries. e.g:

emscripten/src/library.js

Line 31 in 1314e69

getTempRet0__sig: 'i',

[Stuonts]

@sbc100 ,
we also have the same issue with library functions, for example
with emval_new
There is no emval_new__sig in emval.js while there are __sig for some other functions (not all)

[sbc100]

Yes, we tent to add those __sig attributes as needed. Feel free to set a PR at add more if you need them.

[Stuonts]

@sbc100
#17075