Rollup merge of #143716 - workingjubilee:document-some-codegen-backend-stuff, r=bjorn3,fee1-dead
compiler: doc/comment some codegen-for-functions interfaces An out-of-date comment gets updated and some underdocumented functions get documented.
This commit is contained in:
commit
b18064f2f2
3 changed files with 35 additions and 10 deletions
|
|
@ -554,12 +554,33 @@ pub trait BuilderMethods<'a, 'tcx>:
|
|||
/// Called for `StorageDead`
|
||||
fn lifetime_end(&mut self, ptr: Self::Value, size: Size);
|
||||
|
||||
/// "Finally codegen the call"
|
||||
///
|
||||
/// ## Arguments
|
||||
///
|
||||
/// The `fn_attrs`, `fn_abi`, and `instance` arguments are Options because they are advisory.
|
||||
/// They relate to optional codegen enhancements like LLVM CFI, and do not affect ABI per se.
|
||||
/// Any ABI-related transformations should be handled by different, earlier stages of codegen.
|
||||
/// For instance, in the caller of `BuilderMethods::call`.
|
||||
///
|
||||
/// This means that a codegen backend which disregards `fn_attrs`, `fn_abi`, and `instance`
|
||||
/// should still do correct codegen, and code should not be miscompiled if they are omitted.
|
||||
/// It is not a miscompilation in this sense if it fails to run under CFI, other sanitizers, or
|
||||
/// in the context of other compiler-enhanced security features.
|
||||
///
|
||||
/// The typical case that they are None is during the codegen of intrinsics and lang-items,
|
||||
/// as those are "fake functions" with only a trivial ABI if any, et cetera.
|
||||
///
|
||||
/// ## Return
|
||||
///
|
||||
/// Must return the value the function will return so it can be written to the destination,
|
||||
/// assuming the function does not explicitly pass the destination as a pointer in `args`.
|
||||
fn call(
|
||||
&mut self,
|
||||
llty: Self::Type,
|
||||
fn_attrs: Option<&CodegenFnAttrs>,
|
||||
fn_abi: Option<&FnAbi<'tcx, Ty<'tcx>>>,
|
||||
llfn: Self::Value,
|
||||
fn_val: Self::Value,
|
||||
args: &[Self::Value],
|
||||
funclet: Option<&Self::Funclet>,
|
||||
instance: Option<Instance<'tcx>>,
|
||||
|
|
|
|||
|
|
@ -6,16 +6,22 @@ use crate::mir::operand::OperandRef;
|
|||
use crate::mir::place::PlaceRef;
|
||||
|
||||
pub trait IntrinsicCallBuilderMethods<'tcx>: BackendTypes {
|
||||
/// Higher-level interface to emitting calls to intrinsics
|
||||
///
|
||||
/// Remember to add all intrinsics here, in `compiler/rustc_hir_analysis/src/check/mod.rs`,
|
||||
/// and in `library/core/src/intrinsics.rs`; if you need access to any LLVM intrinsics,
|
||||
/// add them to `compiler/rustc_codegen_llvm/src/context.rs`.
|
||||
/// Returns `Err` if another instance should be called instead. This is used to invoke
|
||||
/// intrinsic default bodies in case an intrinsic is not implemented by the backend.
|
||||
///
|
||||
/// NOTE: allowed to call [`BuilderMethods::call`]
|
||||
///
|
||||
/// [`BuilderMethods::call`]: super::builder::BuilderMethods::call
|
||||
fn codegen_intrinsic_call(
|
||||
&mut self,
|
||||
instance: ty::Instance<'tcx>,
|
||||
args: &[OperandRef<'tcx, Self::Value>],
|
||||
result: PlaceRef<'tcx, Self::Value>,
|
||||
result_dest: PlaceRef<'tcx, Self::Value>,
|
||||
span: Span,
|
||||
) -> Result<(), ty::Instance<'tcx>>;
|
||||
|
||||
|
|
|
|||
|
|
@ -991,18 +991,16 @@ fn needs_fn_once_adapter_shim(
|
|||
Ok(false)
|
||||
}
|
||||
(ty::ClosureKind::Fn, ty::ClosureKind::FnMut) => {
|
||||
// The closure fn `llfn` is a `fn(&self, ...)`. We want a
|
||||
// `fn(&mut self, ...)`. In fact, at codegen time, these are
|
||||
// basically the same thing, so we can just return llfn.
|
||||
// The closure fn is a `fn(&self, ...)`, but we want a `fn(&mut self, ...)`.
|
||||
// At codegen time, these are basically the same, so we can just return the closure.
|
||||
Ok(false)
|
||||
}
|
||||
(ty::ClosureKind::Fn | ty::ClosureKind::FnMut, ty::ClosureKind::FnOnce) => {
|
||||
// The closure fn `llfn` is a `fn(&self, ...)` or `fn(&mut
|
||||
// self, ...)`. We want a `fn(self, ...)`. We can produce
|
||||
// this by doing something like:
|
||||
// The closure fn is a `fn(&self, ...)` or `fn(&mut self, ...)`, but
|
||||
// we want a `fn(self, ...)`. We can produce this by doing something like:
|
||||
//
|
||||
// fn call_once(self, ...) { call_mut(&self, ...) }
|
||||
// fn call_once(mut self, ...) { call_mut(&mut self, ...) }
|
||||
// fn call_once(self, ...) { Fn::call(&self, ...) }
|
||||
// fn call_once(mut self, ...) { FnMut::call_mut(&mut self, ...) }
|
||||
//
|
||||
// These are both the same at codegen time.
|
||||
Ok(true)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue