30use rustc_span::{FileName, InnerSpan, Span, SpanData};
31use rustc_structures::CrateType;
32▶use rustc_target::spec::{MergeFunctions, SanitizerSet};
33use tracing::debug;
34
· · ·
106 pub vectorize_loop: bool,
107 pub vectorize_slp: bool,
108▶ pub merge_functions: bool,
109 pub emit_lifetime_markers: bool,
110 pub llvm_plugins: Vec<String>,
· · ·
237
238 // Some targets (namely, NVPTX) interact badly with the
239▶ // MergeFunctions pass. This is because MergeFunctions can generate
240 // new function calls which may interfere with the target calling
241 // convention; e.g. for the NVPTX target, PTX kernels should not
· · ·
240▶ // new function calls which may interfere with the target calling
241 // convention; e.g. for the NVPTX target, PTX kernels should not
242 // call other PTX kernels. MergeFunctions can also be configured to
· · ·
242▶ // call other PTX kernels. MergeFunctions can also be configured to
243 // generate aliases instead, but aliases are not supported by some
244 // backends (again, NVPTX). Therefore, allow targets to opt out of
+ 95 more matches in this file