Shared libraries that don't use a memory are currently assumed to be wasm32

[sbc100]

wasm-ld must be using some kind of heuristic to determine the architecture of shared libraries.

If I create a shared library from the following source, and compile with the a wasm64 target

int library_func() {
  return 42;                                   
}

I get the following error from the linker:

wasm-ld: error: library.so: wasm32 object file can't be linked in wasm64 mode

I'm guessing the same thing might also happen for non-shared object files.

[llvmbot]

@llvm/issue-subscribers-backend-webassembly

Author: Sam Clegg (sbc100)

wasm-ld must be using some kind of heuristic to determine the architecture of shared libraries.

If I create a shared library from the following source, and compile with the a wasm64 target

int library_func() {
  return 42;                                   
}

I get the following error from the linker:

wasm-ld: error: library.so: wasm32 object file can't be linked in wasm64 mode

I'm guessing the same thing might also happen for non-shared object files.

[llvmbot]

@llvm/issue-subscribers-lld-wasm

Author: Sam Clegg (sbc100)

wasm-ld must be using some kind of heuristic to determine the architecture of shared libraries.

If I create a shared library from the following source, and compile with the a wasm64 target

int library_func() {
  return 42;                                   
}

I get the following error from the linker:

wasm-ld: error: library.so: wasm32 object file can't be linked in wasm64 mode

I'm guessing the same thing might also happen for non-shared object files.