| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/CodeGen/ |
| D | FaultMaps.cpp | 74 for (const auto &FFI : FunctionInfos) in serializeToFaultMapSection() local
75 emitFunctionInfo(FFI.first, FFI.second); in serializeToFaultMapSection()
79 const FunctionFaultInfos &FFI) { in emitFunctionInfo() argument
85 LLVM_DEBUG(dbgs() << WFMP << " #faulting PCs: " << FFI.size() << "\n"); in emitFunctionInfo()
86 OS.EmitIntValue(FFI.size(), 4); in emitFunctionInfo()
90 for (auto &Fault : FFI) { in emitFunctionInfo()
120 const FaultMapParser::FunctionFaultInfoAccessor &FFI) { in operator <<() argument
122 << FaultMaps::faultTypeToString((FaultMaps::FaultKind)FFI.getFaultKind()) in operator <<()
123 << ", faulting PC offset: " << FFI.getFaultingPCOffset() in operator <<()
124 << ", handling PC offset: " << FFI.getHandlerPCOffset(); in operator <<()
|
| /third_party/rust/crates/bindgen/book/src/ |
| D | introduction.md | 4 FFI bindings to C and C++ libraries.**
17 `bindgen` produces Rust FFI code allowing you to call into the `cool` library's
|
| D | tutorial-6.md | 4 Rust-y API wrapping the raw FFI bindings in a safe interface. However, there is
5 already a [`bzip2-sys`][bz-sys] crate providing raw FFI bindings, and there is
|
| D | command-line-usage.md | 16 If we wanted to generated Rust FFI bindings from a C header named `input.h` and
|
| D | library-usage.md | 6 `#ifdef`s that affect the shape of the Rust FFI bindings we need to create to
|
| D | tutorial-4.md | 26 our generated Rust FFI structs match what `bindgen` thinks they should be:
|
| D | tutorial-5.md | 5 back out the same as it went in. This is a little wordy using the raw FFI
7 a nice Rust-y API on top of the raw FFI bindings for them. However, since this
|
| /third_party/rust/crates/io-lifetimes/ |
| D | README.md | 26 [provided example FFI bindings]
41 [provided example FFI bindings]: https://github.com/sunfishcode/io-lifetimes/blob/main/src/example_…
75 FFI-safe (on Rust >= 1.63), so they can all be used in FFI [directly]:
126 to support direct FFI usage, niche optimizations so `Option` can support direct
127 FFI usafe as well (on Rust >= 1.63), lifetime-aware `As*`/`Into*`/`From*`
|
| /third_party/rust/crates/cxx/book/src/ |
| D | async.md | 4 Direct FFI of async functions is absolutely in scope for CXX (on C++20 and up)
29 type on the FFI.
|
| D | concepts.md | 7 In CXX, the language of the FFI boundary involves 3 kinds of items:
15 These cannot be passed across the FFI by value but only behind an indirection,
45 // our picture of the FFI boundary is accurate.
|
| D | index.md | 24 The resulting FFI bridge operates at zero or negligible overhead, i.e. no
27 The FFI signatures are able to use native data structures from whichever side
78 feels like C++, not like C-style "FFI glue".
|
| /third_party/icu/icu4c/source/test/testdata/ |
| D | casing.txt | 35 { "aBiσßς/ffi����", "ABIΣSSΣ/FFI����", "" },
36 { "aBiσßς/ffi����", "ABİΣSSΣ/FFI����", "az" } // az same casing as tr
|
| /third_party/rust/crates/bindgen/book/ |
| D | book.toml | 4 description = "`bindgen` automatically generates Rust FFI bindings to C and C++ libraries."
|
| /third_party/rust/crates/cxx/ |
| D | README.md | 1 CXX — safe FFI between Rust and C++
41 The idea is that we define the signatures of both sides of our FFI boundary
56 The resulting FFI bridge operates at zero or negligible overhead, i.e. no
59 The FFI signatures are able to use native types from whichever side they please,
103 // assertions to ensure our picture of the FFI boundary is accurate.
146 As seen in the example, the language of the FFI boundary involves 3 kinds of
153 These cannot be passed across the FFI by value but only behind an indirection,
210 than `extern "C"` C-style signatures as the shared understanding, common FFI use
214 your FFI that is straightforward and doing the remaining few oddball signatures
287 the FFI boundary. Ordinarily in Rust writing your own `extern "C"` blocks is
|
| /third_party/rust/crates/bindgen/ |
| D | README.md | 6 **`bindgen` automatically generates Rust FFI bindings to C (and some C++) libraries.**
19 `bindgen` produces Rust FFI code allowing you to call into the `doggo` library's
|
| D | README_zh.md | 6 `bindgen` 自动生成Rust与C（和一些C++）库的FFI绑定。
19 `bindgen`产生Rust FFI代码，允许调用`doggo`库的函数并使用其类型：
|
| /third_party/rust/crates/cxx/book/src/binding/ |
| D | fn.md | 34 FFI](../async.md). See the example code on that page.
|
| D | result.md | 27 FFI. The Rust *implementation* (outside of the bridge module) may pick any error
85 FFI. The resulting error type created by CXX when an `extern "C++"` function
|
| /third_party/rust/crates/rust-openssl/openssl-sys/ |
| D | Cargo.toml | 9 description = "FFI bindings to OpenSSL"
|
| D | BUILD.gn | 26 cargo_pkg_description = "FFI bindings to OpenSSL"
|
| /third_party/rust/crates/libc/ |
| D | Cargo.toml | 15 Raw FFI bindings to platform libraries like libc.
|
| /third_party/rust/crates/clang-sys/ |
| D | CHANGELOG.md | 342 - Added implementations of `Deref` for opaque FFI structs
403 - Added implementations of `Default` for FFI structs
482 - Added derivations of `Debug` for FFI structs
487 - Added derivations of `PartialOrd` and `Ord` for FFI enums
|
| /third_party/rust/crates/bindgen/bindgen-cli/ |
| D | Cargo.toml | 5 description = "Automatically generates Rust FFI bindings to C and C++ libraries."
|
| D | BUILD.gn | 26 "Automatically generates Rust FFI bindings to C and C++ libraries."
|
| /third_party/rust/crates/bindgen/bindgen/ |
| D | Cargo.toml | 8 description = "Automatically generates Rust FFI bindings to C and C++ libraries."
|