diff options
| author | Trevor Gross <tmgross@umich.edu> | 2025-03-18 10:13:47 +0000 |
|---|---|---|
| committer | Trevor Gross <t.gross35@gmail.com> | 2025-03-18 05:35:19 -0500 |
| commit | a179959e0bc8dc061bcf9ec841b6a8b8b516e683 (patch) | |
| tree | f537841c5675116111d46f06d2a3c7105e3d2730 /tests/codegen/patchable-function-entry/patchable-function-entry-one-flag.rs | |
| parent | 590a56483cc32e2cd38a6de76c71c319db997360 (diff) | |
| download | rust-a179959e0bc8dc061bcf9ec841b6a8b8b516e683.tar.gz rust-a179959e0bc8dc061bcf9ec841b6a8b8b516e683.zip | |
Move `examples/intrinsics.rs` to its own crate
Currently there is an interesting situation with the way features get enabled; `testcrate` enables `mangled-names`, but the `intrinsics.rs` example requires this feature be disabled (otherwise the test fails with missing symbols, as expected). This is also the reason that `testcrate` is not a default workspace member, meaning `cargo test` doesn't actually run `testcrate`'s tests; making it a default member would mean that `compiler-builtins/mangled-names` gets enabled when `examples/intrinsics.rs` gets built, due to the way features get unified. Simplify the situation by making moving the example to its own crate as `builtins-test-intrinsics`. This also means `testcrate` can become a default member so it is included in `cargo check` or `cargo test` when run at the workspace root. `testcrate` and `builtins-test-intrinsics` still can't be built at the same time since there isn't a straightforward way to have Cargo build `compiler-builtins` twice with different features. This is a side effect of us using non-additive features, but there isn't really a better option since enabling both mangled and unmangled names would render `builtins-test-intrinsics` useless.
Diffstat (limited to 'tests/codegen/patchable-function-entry/patchable-function-entry-one-flag.rs')
0 files changed, 0 insertions, 0 deletions
