Lines Matching refs:API

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