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