I observed errors like the following when trying to upgrade our
LLVM from 15 to 19.
```
AOT module load failed: resolve symbol .srodata.cst8 failed
```
The concept itself has been available since LLVM 9.
I don't know what exactly happened to trigger the use of it.
cf. https://reviews.llvm.org/D57493
with the recent version of LLVM, wamrc --size-level=1 often
generates R_X86_64_32S relocations which fail on load with
the infamous error:
"relocation truncated to fit R_X86_64_32S failed"
it seems that these relocations are often for jump tables.
this commit workarounds it with --size-level=0.
an alternative is to disable jump tables. (although it seems that
jump tables are not the only source of these relocations.)
cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3035
it might be better to do this in wamrc itself. however, currently
target info is not available there in case of native compilation.
related: https://github.com/bytecodealliance/wasm-micro-runtime/issues/3356
- it's unused
- valgrind is basically a linux-only software.
it isn't a good idea to make it a hard requirement.
if we want to use valgrind, it's better to introduce
a separate option to control it.
* **Notice**: The python package `wamr.wamrapi.wamr`need python >= `3.10`.
* **Notice**: The python package `wamr.wamrapi.wamr`requires a python version >= `3.10`.
## Setup
## Setup
### Pre-requisites
### Pre-requisites
#### Install requirements
Before proceeding it is necessary to make sure your Python environment is correctly configured. To do ths open a terminal session in this directory and perfom the following:
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.