From b376bc3f60778c03c61eaa64e448769fac744a4f Mon Sep 17 00:00:00 2001 From: Jakub Chlanda Date: Tue, 18 Aug 2026 09:45:08 +0000 Subject: [PATCH] Tighten the language used for documenting `TargetOptions::llvm_abiname` `MCOptions` is the name of the variable commonly used for instances of `MCTargetOptions`. Use the proper type name instead. --- compiler/rustc_target/src/spec/mod.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/compiler/rustc_target/src/spec/mod.rs b/compiler/rustc_target/src/spec/mod.rs index b3865eeaf6bf8..ff6cade232523 100644 --- a/compiler/rustc_target/src/spec/mod.rs +++ b/compiler/rustc_target/src/spec/mod.rs @@ -2651,8 +2651,8 @@ pub struct TargetOptions { /// Use LLVM intrinsic for mcount function name pub llvm_mcount_intrinsic: Option>, - /// LLVM ABI name, corresponds to the '-mabi' parameter available in multilib C compilers - /// and the `-target-abi` flag in llc. In the LLVM API this is `MCOptions.ABIName`. + /// LLVM ABI name, corresponds to the '-mabi' parameter available in multilib C compilers and + /// the `-target-abi` flag in llc. In the LLVM API this is `MCTargetOptions::ABIName`. pub llvm_abiname: LlvmAbi, /// Control the float ABI to use, for architectures that support it. The only architecture we