en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/src/profiling.rs#99ecf728 Debug: create private code memories per store when debugging is enabled. (#12051)* Debug: create private code memories per store when debugging is enabled.This will allow patching code to implement e.g. breakpoints. (That is,for now the copies are redundant, but soon they will not be.)This change follows the discussion [here] and offline to define a fewtypes that better encapsulate the distinction we want to enforce.Basically, there is almost never a bare `CodeMemory`; they are alwayswrapped in an `EngineCode` or `StoreCode`, the latter being a per-storeinstance of the former. Accessors are moved to the relevant place sothat, for example, one cannot get a pointer to a Wasm function's bodywithout being in the context of a `Store` where the containing modulehas been registered. The registry then returns a `ModuleWithCode` thatboxes up a `Module` reference and `StoreCode` together for cases wherewe need both the metadata from the module and the raw code to derivesomething.The only case where we return raw code pointers to the `EngineCode`directly have to do with Wasm-to-array trampolines: in some cases, e.g.`InstancePre` pre-creating data structures with references to hostfunctions, it breaks our expected performance characteristics to makethe function pointers store-specific. This is fine as long as theWasm-to-array trampolines never bake in direct calls to Wasm functions;the strong invariant is that Wasm functions never execute from`EngineCode` directly. Some parts of the component runtime would alsohave to be substantially refactored if we wanted to do away with thisexception.The per-`Store` module registry is substantially refactored in this PR.I got rid of the modules-without-code distinction (the case where amodule only has trampolines and no defined functions still works fine),and organized the BTreeMaps to key on start address rather than endaddress, which I find a little more intuitive (one then queries with thedual to the range -- 0-up-to-PC and last entry found).[here]: https://github.com/bytecodealliance/wasmtime/pull/12051#pullrequestreview-3493711812* Review feedback: do not assume a reasonable code alignment; error when it cannot be known* Review feedback: fail properly in profiler when we are cloning code* Fix guest-profiler C API.* Review feedback: make private-code representation impossible in non-debugging-support builds.* Add TODO comment referencing issue for cloning only .text.* clang-format* Review feedback: add back Component::image_range.* Review feedback: error on registering profiling metadata when debug is enabled.* rustfmt* Remove early bail on profiling-data registration when debugging is enabled: this always happens so we cannot error out. List of files: /wasmtime-44.0.1/crates/c-api/src/profiling.rs Wed, 03 Dec 2025 01:18:00 +0000 Chris Fallin <chris@cfallin.org> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/src/profiling.rs#c3177fc4 Guest Profiling suport for component model (#10507)* Guest Profiling suport for component modelThis change adds support for using guest profiling with thecomponent model. In addition to the core change to supportattributing stack frames to constituient modules within a component,the cli `run` and `serve` commands are also updated to supportusing the `--profile=guest` cli option with components.https://github.com/bytecodealliance/wasmtime/issues/8773https://github.com/bytecodealliance/wasmtime/issues/7669* fixup! Guest Profiling suport for component model List of files: /wasmtime-44.0.1/crates/c-api/src/profiling.rs Wed, 02 Apr 2025 19:34:04 +0000 Paul Osborne <paul.osborne@fastly.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/src/profiling.rs#ae84e6ed Enable `unsafe-attr-outside-unsafe` 2024 edition lint (#9964)* Enable `unsafe-attr-outside-unsafe` 2024 edition lintThis commit enables the `unsafe-attr-outside-unsafe` lint in rustc usedin transitioning to the 2024 edition. This requires that the`#[no_mangle]` attribute is replaced in favor of `#[unsafe(no_mangle)]`.This mostly affects the C API of wasmtime and most of the changes hereare a simple search/replace.* Another attribute update* Fix command adapter build List of files: /wasmtime-44.0.1/crates/c-api/src/profiling.rs Thu, 09 Jan 2025 21:05:55 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/src/profiling.rs#7d0bdcce Accept explicit CPU delta time in GuestProfiler (#7873)* Add function accepting explicit CPU delta time to GuestProfiler* Remove unused import* Modify existing signature instead of adding new* Use qualified Duration instead of import to prevent unused warnings when building without features List of files: /wasmtime-44.0.1/crates/c-api/src/profiling.rs Wed, 07 Feb 2024 02:16:27 +0000 Milek7 <Milek7@users.noreply.github.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/src/profiling.rs#d4eaacd6 Add C API for GuestProfiler (#7854)* Add C API for GuestProfiler* GuestProfiler C API: remove unsafe and add docs* Fix clang-format complaints* rename to wasmtime_guestprofiler_t for consistency, change to passing tuples by struct type, clarify docs* rustfmt* out is marked "own" too* gate on profiling feature List of files: /wasmtime-44.0.1/crates/c-api/src/profiling.rs Mon, 05 Feb 2024 17:34:19 +0000 Milek7 <Milek7@users.noreply.github.com>