Module abi_check 

This module ensures that if a function’s ABI requires a particular target feature, that target feature is enabled both on the callee and all callers.

Re-exports

use rustc_abi::BackendRepr; 🔒

use rustc_abi::CanonAbi; 🔒

use rustc_abi::ExternAbi; 🔒

use rustc_abi::RegKind; 🔒

use rustc_abi::X86Call; 🔒

use rustc_hir::CRATE_HIR_ID; 🔒

use rustc_hir::HirId; 🔒

use rustc_middle::mir; 🔒

use rustc_middle::mir::Location; 🔒

use rustc_middle::mir::traversal; 🔒

use rustc_middle::ty::layout::FnAbiRequest; 🔒

use rustc_middle::ty::layout::codegen_handle_fn_abi_err; 🔒

use rustc_middle::ty; 🔒

use rustc_middle::ty::Instance; 🔒

use rustc_middle::ty::InstanceKind; 🔒

use rustc_middle::ty::Ty; 🔒

use rustc_middle::ty::TyCtxt; 🔒

use rustc_span::def_id::DefId; 🔒

use rustc_span::DUMMY_SP; 🔒

use rustc_span::Span; 🔒

use rustc_span::Symbol; 🔒

use rustc_span::sym; 🔒

use rustc_target::callconv::FnAbi; 🔒

use rustc_target::callconv::PassMode; 🔒

use crate::diagnostics; 🔒

Enums

UsesVectorRegisters 🔒

Are vector registers used?

Functions

check_call_site_abi 🔒

Check the ABI at a call site, emitting an error when:

check_callees_abi 🔒

check_feature_dependent_abi 🔒

check_instance_abi 🔒

Checks the ABI of an Instance, emitting an error when:

do_check_simd_vector_abi 🔒

Checks whether a certain function ABI is compatible with the target features currently enabled for a certain function. is_call indicates whether this is a call-site check or a definition-site check; this is only relevant for the wording in the emitted error.

do_check_unsized_params 🔒

Emit an error when a non-rustic ABI has unsized parameters. Unsized types do not have a stable layout, so should not be used with stable ABIs. is_call indicates whether this is a call-site check or a definition-site check; this is only relevant for the wording in the emitted error.

passes_vectors_by_value 🔒

Determines whether the combination of mode and repr will use fixed vector registers, scalable vector registers or no vector registers.