32use rustc_span::source_map::SourceMap;
33use rustc_span::{FileName, InnerSpan, Span, SpanData};
34▶use rustc_target::spec::{MergeFunctions, SanitizerSet};
35use tracing::debug;
36
· · ·
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>,
· · ·
224
225 // Some targets (namely, NVPTX) interact badly with the
226▶ // MergeFunctions pass. This is because MergeFunctions can generate
227 // new function calls which may interfere with the target calling
228 // convention; e.g. for the NVPTX target, PTX kernels should not
· · ·
227▶ // new function calls which may interfere with the target calling
228 // convention; e.g. for the NVPTX target, PTX kernels should not
229 // call other PTX kernels. MergeFunctions can also be configured to
· · ·
229▶ // call other PTX kernels. MergeFunctions can also be configured to
230 // generate aliases instead, but aliases are not supported by some
231 // backends (again, NVPTX). Therefore, allow targets to opt out of
+ 94 more matches in this file