mirror of
https://github.com/rust-lang/rust.git
synced 2025-10-31 04:57:19 +00:00
8c8225afe8
Previously `-Zprint-mono-items` would override the mono item collection strategy. When debugging one doesn't want to change the behaviour, so this was counter productive. Additionally, the produced behaviour was artificial and might never arise without using the option in the first place (`-Zprint-mono-items=eager` without `-Clink-dead-code`). Finally, the option was incorrectly marked as `UNTRACKED`. Resolve those issues, by turning `-Zprint-mono-items` into a boolean flag that prints results of mono item collection without changing the behaviour of mono item collection. For codegen-units test incorporate `-Zprint-mono-items` flag directly into compiletest tool. Test changes are mechanical. `-Zprint-mono-items=lazy` was removed without additional changes, and `-Zprint-mono-items=eager` was turned into `-Clink-dead-code`. Linking dead code disables internalization, so tests have been updated accordingly.
71 lines
2.8 KiB
Plaintext
71 lines
2.8 KiB
Plaintext
monomorphize_abi_error_disabled_vector_type =
|
|
this function {$is_call ->
|
|
[true] call
|
|
*[false] definition
|
|
} uses SIMD vector type `{$ty}` which (with the chosen ABI) requires the `{$required_feature}` target feature, which is not enabled{$is_call ->
|
|
[true] {" "}in the caller
|
|
*[false] {""}
|
|
}
|
|
.label = function {$is_call ->
|
|
[true] called
|
|
*[false] defined
|
|
} here
|
|
.help = consider enabling it globally (`-C target-feature=+{$required_feature}`) or locally (`#[target_feature(enable="{$required_feature}")]`)
|
|
|
|
monomorphize_abi_error_unsupported_vector_type =
|
|
this function {$is_call ->
|
|
[true] call
|
|
*[false] definition
|
|
} uses SIMD vector type `{$ty}` which is not currently supported with the chosen ABI
|
|
.label = function {$is_call ->
|
|
[true] called
|
|
*[false] defined
|
|
} here
|
|
|
|
monomorphize_abi_required_target_feature =
|
|
this function {$is_call ->
|
|
[true] call
|
|
*[false] definition
|
|
} uses ABI "{$abi}" which requires the `{$required_feature}` target feature, which is not enabled{$is_call ->
|
|
[true] {" "}in the caller
|
|
*[false] {""}
|
|
}
|
|
.label = function {$is_call ->
|
|
[true] called
|
|
*[false] defined
|
|
} here
|
|
.help = consider enabling it globally (`-C target-feature=+{$required_feature}`) or locally (`#[target_feature(enable="{$required_feature}")]`)
|
|
|
|
monomorphize_couldnt_dump_mono_stats =
|
|
unexpected error occurred while dumping monomorphization stats: {$error}
|
|
|
|
monomorphize_encountered_error_while_instantiating =
|
|
the above error was encountered while instantiating `{$formatted_item}`
|
|
|
|
monomorphize_large_assignments =
|
|
moving {$size} bytes
|
|
.label = value moved from here
|
|
.note = The current maximum size is {$limit}, but it can be customized with the move_size_limit attribute: `#![move_size_limit = "..."]`
|
|
|
|
monomorphize_no_optimized_mir =
|
|
missing optimized MIR for `{$instance}` in the crate `{$crate_name}`
|
|
.note = missing optimized MIR for this item (was the crate `{$crate_name}` compiled with `--emit=metadata`?)
|
|
|
|
monomorphize_recursion_limit =
|
|
reached the recursion limit while instantiating `{$shrunk}`
|
|
.note = `{$def_path_str}` defined here
|
|
|
|
monomorphize_start_not_found = using `fn main` requires the standard library
|
|
.help = use `#![no_main]` to bypass the Rust generated entrypoint and declare a platform specific entrypoint yourself, usually with `#[no_mangle]`
|
|
|
|
monomorphize_symbol_already_defined = symbol `{$symbol}` is already defined
|
|
|
|
monomorphize_wasm_c_abi_transition =
|
|
this function {$is_call ->
|
|
[true] call
|
|
*[false] definition
|
|
} involves an argument of type `{$ty}` which is affected by the wasm ABI transition
|
|
.help = the "C" ABI Rust uses on wasm32-unknown-unknown will change to align with the standard "C" ABI for this target
|
|
|
|
monomorphize_written_to_path = the full type name has been written to '{$path}'
|