-
### Proposal:
I feel like the ABI should have an ``awaitable_set_debug()`` ABI function that users can call when they compile their extension with ``_DEBUG``/``DEBUG`` defined:
- In debug when tha…
-
# Problem
This issue needs to exist so I can submit a pull request to solve it, because of our voting procedures.
The problem is described in some detail in https://arxiv.org/abs/2308.11214. I …
-
When LLVM needs to call a builtin (such as `__truncdfhf2` or `__addtf3`), it will use whatever ABI is the default for the target features of the function that is currently being compiled. This means t…
-
I use 0.7.6 and cannot compile it due to errors inside alloy-json-abi.
Here's the output when building:
![ksnip_20241024-133033](https://github.com/user-attachments/assets/581cd52f-06a8-4c96-829…
-
Platforms: rocm, inductor
This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_constant_abi_compatible_cuda&suite=AOTInductorTestABICo…
-
We should remove the build script if possible, if not we should make sure that it is very robust. One very interesting problem would be related to the comment below:
Since that's a …
-
See: https://github.com/loongson/la-abi-specs/blob/release/lapcs.adoc
-
`Boost.Context` doesn't contain assembler code for `abi=aapcs, address-model=64, architecture=arm, binary-format=pe, toolset=gcc` which manifest in the following error when building Boost. I'm not sur…
-
Todo:
- Check compatility of dynamic c library against zlib and zlib-ng (Using [Abigail Framwork / abidiff](https://sourceware.org/libabigail/manual/abidiff.html))
- In the future: setup CI
-
As an Issuer,
I want to pass my custom ABI to the SDK to get contextualized errors,
So that my application can handle error cases seemlessly
----
Currently, only the errors defined in the `DefaultPo…