Skip to content

Conversation

@mmorel-35
Copy link
Contributor

@mmorel-35 mmorel-35 commented Jan 22, 2026

Description

add wasmedge-llvm engine

@PiotrSikora
Copy link
Member

Nitpicking, but AFAIK those interpreters are custom and unrelated to LLVM, so the naming is wrong.

Also, there are more modes available (e.g. WAMR has "Fast JIT" and "LLVM JIT"), although they're not hooked into Proxy-Wasm C++ Host (yet?).

@mmorel-35 mmorel-35 force-pushed the engine-llvm branch 2 times, most recently from 0ee866e to ba375ce Compare January 22, 2026 22:25
@mmorel-35 mmorel-35 changed the title refactor: unify WAMR engine configuration and add LLVM mode support add wasmedge-aot engine Jan 22, 2026
@mmorel-35
Copy link
Contributor Author

mmorel-35 commented Jan 22, 2026

Alright, I better focus on just adding wasmedge-llvm engine

@mmorel-35 mmorel-35 force-pushed the engine-llvm branch 3 times, most recently from 1f190b0 to 2316253 Compare January 22, 2026 22:35
@mmorel-35 mmorel-35 changed the title add wasmedge-aot engine add wasmedge-llvm engine Jan 22, 2026
@mmorel-35 mmorel-35 marked this pull request as ready for review January 22, 2026 23:00
@mmorel-35 mmorel-35 marked this pull request as draft January 23, 2026 08:12
@mmorel-35 mmorel-35 force-pushed the engine-llvm branch 7 times, most recently from 067991f to ae0f162 Compare January 23, 2026 13:37
Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants