rust/messages.ftl

codegen_gcc_invalid_minimum_alignment =
    invalid minimum global alignment: {$err}

codegen_gcc_lto_not_supported =
    LTO is not supported. You may get a linker error.

codegen_gcc_tied_target_features = the target features {$features} must all be either enabled or disabled together
    .help = add the missing features in a `target_feature` attribute

codegen_gcc_unwinding_inline_asm =
    GCC backend does not support unwinding from inline asm
Ensure Fluent messages are in alphabetical order 2023-05-22 20:51:25 -05:00			`codegen_gcc_invalid_minimum_alignment =`
			`invalid minimum global alignment: {$err}`
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com> 2022-10-13 04:13:02 -05:00
Ensure Fluent messages are in alphabetical order 2023-05-22 20:51:25 -05:00			`codegen_gcc_lto_not_supported =`
			`LTO is not supported. You may get a linker error.`
Fix for diagnostics 2023-03-05 11:31:16 -06:00
			`codegen_gcc_tied_target_features = the target features {$features} must all be either enabled or disabled together`
			.help = add the missing features in a `target_feature` attribute
Ensure Fluent messages are in alphabetical order 2023-05-22 20:51:25 -05:00
			`codegen_gcc_unwinding_inline_asm =`
			`GCC backend does not support unwinding from inline asm`