pub struct Report {
pub dumps: Vec<Dump>,
pub broke: Vec<String>,
pub spent: Vec<(&'static str, u32)>,
pub remarks: Vec<Remark>,
}Expand description
What running the pipeline produced beyond the changed module.
Fields§
§dumps: Vec<Dump>The dumps asked for, in the order they were taken. The manager does not write files,
because nothing below the driver in spec/18-package-layout.md knows what a file is.
broke: Vec<String>A pass that left the IR in a state the verifier refuses, named, with what it said.
spent: Vec<(&'static str, u32)>How much fuel each pass spent, which is the number a bisection halves.
remarks: Vec<Remark>What every pass said about every function, in the order the passes ran and then in the
order the module holds its functions. This is what -fopt-info prints.
Implementations§
Source§impl Report
impl Report
Sourcepub fn totals(&self, pass: &str) -> Stats
pub fn totals(&self, pass: &str) -> Stats
Everything one pass said across the whole module, added up.
The counts of an event are addable across functions because an event names a site in a
pass rather than a fact about a program, which is the reason crate::stats::Event::what
is a fixed string.