From f6e5e32dae508f4a1fd488632315e80e905b6f31 Mon Sep 17 00:00:00 2001 From: "liang.he@intel.com" Date: Mon, 4 Nov 2024 17:23:28 +0800 Subject: [PATCH] [wamr] Meeting notes for 11-04 --- wamr/2024/wamr-11-04.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/wamr/2024/wamr-11-04.md b/wamr/2024/wamr-11-04.md index 2a4508e..6ddb7e7 100644 --- a/wamr/2024/wamr-11-04.md +++ b/wamr/2024/wamr-11-04.md @@ -9,15 +9,23 @@ 3. Announcements a. _Submit a PR to add your announcement here_ 4. Other agenda items - b. _Submit a PR to add your item here_ + - status of instantiation linking + - requirements ## Attendees -* TODO +- Jun Xu (Intel) +- Liang He (Intel) +- Trenner, Thomas (Siemens) +- Tacke, Dominik (Siemens) ## Notes -* TODO +- Siemens has a requirement. It involves updating a running Wasm module without completely stopping it. The update will be a tiny patch. A brief pause and resume are only acceptable if no running status is lost. Siemens is attempting to do this using the shared heap/memory and multi-memory features, but both present challenges. + +- Another requirement from Siemens concerns AOT debugging. The current system allows the debugger to see parts of the runtime and/or embedding code. However, in Siemens' scenario, both sets of code should be hidden from Wasm developers, even in assembly mode. + +- Siemens also updated the status of exception handling. There are several unanswered questions about handling exceptions that a Wasm module does not catch. Since Wamr is written in C, which lacks language-level exception handling, this issue is complex and fraught with potential problems. Therefore, a broad community discussion is needed. Siemens will open several issues to start the conversation. ## Action Items