Lines Matching refs:API

1 # MLIR C API
3 **Current status: Under development, API unstable, built by default.**
10 name mangling and memory model differences. Although the C API for MLIR can be
12 language- or library-specific constructs. Therefore the API tends towards
15 **Note:** while the C API is expected to be more stable than C++ API, it
20 The API is provided for core IR components (attributes, blocks, operations,
22 The core IR API is intentionally low-level, e.g. exposes a plain list of
24 names to them. Users of specific dialects are expected to wrap the core API in a
30 C++. They are not intended to be inspected by the API users (and, in many cases,
76 check if an object is null by using `mlirXIsNull(MlirX)`. API functions do _not_
77 expect null objects as arguments unless explicitly stated otherwise. API
85 base classes. Type hierarchies are exposed to C API through naming conventions
107 segment of a string. This segment may or may not be null-terminated. In C API,
137 The API adopts the following patterns for recurrent functionality in MLIR.
186 ## Extending the API
196 the inverse conversion. Once the C++ object is available, the API implementation
198 inside other API calls.