Skip to content

SetjmpLongjmp.md: update for LLVM 20 #523

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

SetjmpLongjmp.md: update for LLVM 20 #523

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 16 additions & 14 deletions SetjmpLongjmp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,13 +11,13 @@ To build an application using setjmp/longjmp, you need two things:
### Example without LTO

```shell
clang -Os -mllvm -wasm-enable-sjlj -o your_app.wasm your_app.c -lsetjmp
clang -Os -mllvm -wasm-enable-sjlj -o your_app.phase3.wasm your_app.c -lsetjmp
```

### Example with LTO

```shell
clang -Os -flto=full -mllvm -wasm-enable-sjlj -Wl,-mllvm,-wasm-enable-sjlj -o your_app.wasm your_app.c -lsetjmp
clang -Os -flto=full -mllvm -wasm-enable-sjlj -Wl,-mllvm,-wasm-enable-sjlj -o your_app.phase3.wasm your_app.c -lsetjmp
```

## Run an application
Expand All @@ -34,38 +34,40 @@ Unfortunately, there are two incompatible versions of

### Example with the latest exception handling proposal

Because the current version of WASI-SDK produces an old version
of [exception handling proposal] instructions, if your runtime
implements the latest version of the proposal, you need to convert
your module to the latest version.
By default, the current version of WASI-SDK produces the
"phase3" version of [exception handling proposal] instructions.

[toywasm] is an example of such runtimes.
You can tell the llvm to produce the latest version of proposal by
specifying `-mllvm -wasm-use-legacy-eh=false`. This is expected
to be the default in a future version.

You can use binaryen `wasm-opt` command for the conversion.
Alternatively, you can use binaryen `wasm-opt` command to convert
existing modules from the "phase3" version to the "exnref" version.

```shell
wasm-opt --translate-to-exnref -all -o your_app.exnref.wasm your_app.wasm
wasm-opt --translate-to-exnref -all -o your_app.wasm your_app.phase3.wasm
```

Then you can run it with a runtime supporting the latest version of
[exception handling proposal].
Then you can run it with a runtime supporting the "exnref" version of
the proposal.
[toywasm] is an example of such runtimes.

```shell
toywasm --wasi your_app.exnref.wasm
toywasm --wasi your_app.wasm
```
(You may need to enable the support with `-D TOYWASM_ENABLE_WASM_EXCEPTION_HANDLING=ON`.)

### Example with the phase3 exception handling proposal (a bit older version)

If your runtime supports the [phase3] version of
[exception handling proposal], which is the same version as what WASI-SDK
currently produces, you can run the produced module as it is.
currently produces by default, you can run the produced module as it is.

For example, the classic interpreter of [wasm-micro-runtime] is
one of such runtimes.

```shell
iwasm your_app.wasm
iwasm your_app.phase3.wasm
```
(You may need to enable the support with `-D WAMR_BUILD_EXCE_HANDLING=1 -D WAMR_BUILD_FAST_INTERP=0`.)

Expand Down
Loading