Searched refs:layer (Results 1 – 12 of 12) sorted by relevance
76 for layer in self.0.layers() { in fmt()77 f.entry(&layer); in fmt()265 for layer in &mut expected { in assert_stratification()266 layer.sort(); in assert_stratification()273 .map(|layer| { in assert_stratification()274 let mut layer = layer.iter().map(|f| f.as_u32()).collect::<Vec<_>>(); in assert_stratification() localVariable275 layer.sort(); in assert_stratification()276 layer in assert_stratification()
71 ;; memory and each layer otherwise is a list of the previous layer.73 ;; Each layer-of-lists is `$pages` large.84 ;; Case of $depth>0 meaning that this is a list-of-lists layer.86 ;; layer down by recursing.102 ;; layer's list.
5 - `interpret.ml`: a shim layer for calling the Wasm spec code and exposing it
5 This crate is structured as an optional layer on top of cranelift-codegen.
64 [MC](https://llvm.org/docs/CodeGenerator.html#the-mc-layer)65 MC serves as the output abstraction layer and is the basis for LLVM's99 Cranelift would add a separate IR layer, or possibly an separate IR, to support123 Module functionality in Cranelift is provided as an optional library layer, in
133 `inst.isle` layer. Either way, the important thing is that the lowering rules145 constraints are fulfilled a layer below the lowering rules (in `inst.isle` or in
682 for layer in strata.layers() { in compile_with_inlining()689 layer_outputs.extend(layer.iter().map(|f| outputs[*f].take().unwrap())); in compile_with_inlining()744 for (f, func) in layer.iter().zip(layer_outputs.drain(..)) { in compile_with_inlining()
53 full-strength optimizer would either use an IR layer on top of it
350 /// currently an optional timeout applicable to the transport layer of the666 /// protocol's transport layer.
347 /// currently an optional timeout applicable to the transport layer of the
344 ;; Here the top-layer of this rule matches the `(select ...)` node where 0 is
2489 notes = "Tiny layer on top of the proc macro crate, found no unsafe or system usage"