en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/trap.cc#b856261d refactor recursive reentrance checks (#12349)* refactor recursive reentrance checksThis commit makes a few changes related to recursive reentrance checks, instancepoisoning, etc.:- Implements the more restrictive lift/lower rules described in https://github.com/WebAssembly/component-model/pull/589 such that a component instance may not lower a function lifted by one of its ancestors, nor vice-versa. Any such lower will result in a fused adapter which traps unconditionally, preventing guest-to-guest recursive reentrance without requiring data flow analysis. - Note that this required updating several WAST tests which were violating the new rule, including some in the `tests/component-model` Git submodule, which I've updated. - This is handled entirely in the `fact` module now; I've removed the `AlwaysTrap` case previously handled by `wasmtime-cranelift`.- Removes `FLAG_MAY_ENTER` from `InstanceFlags`. It is no longer needed for guest-to-guest calls due to the above, and for guest-to-host-to-guest calls we can rely on either `FLAG_NEEDS_POST_RETURN` for sync-lifted functions or the `GuestTask` call stack for async-lifted functions.- Adds a `StoreOpaque::trapped` field which is set when _any_ instance belonging to that store traps, at which point the entire store is considered poisoned, meaning no instance belonging to it may be entered. This prevents indeterminant concurrent task state left over from the trapping instance from leaking into other instances.Note that this does _not_ include code to push and pop `GuestTask` instances forguest-to-guest sync-to-sync calls, nor for host-to-guest calls using e.g. thesynchronous `Func::call` API, so certain intrinsics which expect a `GuestTask`to be present such as `backpressure.inc` will still fail in such cases. I'lladdress that in a later PR.Also note that I made a small change to `wasmtime-wit-bindgen`, adding a `Send`bound on the `T` type parameter for `store | async` functions. This allowed meto recursively call `{Typed}Func::call_concurrent` from inside a host function,and it doesn't have any downsides AFAICT.Fixes #12128* bless bindgen expansions* bless disas tests* address review feedback* sync `trap.h` with `trap_encoding.rs`...and add const assertions to `trap.rs` to help avoid future divergence. List of files: /wasmtime-44.0.1/crates/c-api/tests/trap.cc Wed, 14 Jan 2026 22:27:49 +0000 Joel Dice <joel.dice@fermyon.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/trap.cc#23e27bad c-api: new wasmtime_trap_new_code function (#10765)* c-api: new wasmtime_trap_new_code function* review comments* remove accidental include List of files: /wasmtime-44.0.1/crates/c-api/tests/trap.cc Thu, 15 May 2025 05:56:59 +0000 Carmen <carmen@donn.dev> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/trap.cc#a045eaa9 Run `clang-format` over more files (#10689)We were already running it over most `*.c` files and other ones butforgot the `*.hh` and `*.cc` extensions which are being used for C++bindings, so add those in and then run the formatter. List of files: /wasmtime-44.0.1/crates/c-api/tests/trap.cc Mon, 28 Apr 2025 20:38:14 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/trap.cc#d06f6517 Move the C++ `Trap` and related types to its own header (#10647) List of files: /wasmtime-44.0.1/crates/c-api/tests/trap.cc Tue, 22 Apr 2025 23:43:18 +0000 Alex Crichton <alex@alexcrichton.com>