|
Revision tags: dev, v36.0.9, v44.0.1, v43.0.2, v36.0.8, v24.0.8, v44.0.0, v43.0.1, v42.0.2, v36.0.7, v24.0.7, v43.0.0, v42.0.1, v41.0.4, v42.0.0, v40.0.4, v36.0.6, v24.0.6, v41.0.3, v41.0.2, v41.0.1, v36.0.5, v40.0.3, v41.0.0, v36.0.4, v39.0.2, v40.0.2, v40.0.1, v40.0.0 |
|
| #
9bb96d51 |
| 02-Dec-2025 |
Nick Fitzgerald <[email protected]> |
Add `Config::without_compiler` (#12089)
* Add `Config::without_compiler`
This provides us an allocation-free path for constructing a `Config`.
Why not rely on builds when `cfg(not(any(feature = "c
Add `Config::without_compiler` (#12089)
* Add `Config::without_compiler`
This provides us an allocation-free path for constructing a `Config`.
Why not rely on builds when `cfg(not(any(feature = "cranelift", feature =
"winch")))`? Because we need to test our various OOM-handling and
allocation-free code paths in this workspace, and without some way to create a
config without a compiler otherwise, cargo's feature resolver will enable those
features in the workspace, enabling the compiler in the config, but we don't
intend to make compiler configurations handle OOM.
* Quiet unused mut warnings
* Move default compiler flags into builder
show more ...
|