[mlir][python] Support Arbitrary Precision Integers in MLIR C API and Python Bindings (#177733)
This PR extends the MLIR C API and Python bindings to support
**arbitrary-precision integers (`APInt`)**, overcoming the previous
limitation where `IntegerAttr` values were restricted to 64 bits.
Cryptographic applications often require integer types much larger than
standard machine words (e.g., the 256-bit modulus for the BN254 curve).
Previously, attempting to bind these values resulted in truncation or
errors. This PR exposes the underlying word-based `APInt` structure via
the C API and updates the Python bindings to seamlessly handle Python's
arbitrary-precision integers.
p5-Test-Future-IO-Impl: update to 0.17.
0.17 2026-01-18
[CHANGES]
* Added tests for `poll` method
[BUGFIXES]
* Account for the fact that read or write IO operations may have
already happened before they are cancelled
* Clear the EAGAIN error from `$wr` filehandle in EAGAIN write test
to stop perl writing annoying warnings during test
0.16 2026-01-07
[BUGFIXES]
* Be less sensitive to `->send` failure in peer-closed case, as OS
behaviour differs here
* sleep() unconditionally after closing listening server in connect
test, as most OSes need it. 100msec is sufficient
p5-CPAN-Meta-Requirements: update to 2.144.
2.144 2026-01-22 16:12:20-05:00 America/New_York
- Remove code meant to cope with running on v5.8, when v5.10 is the minimum
required perl!
- Normalize away ">= 0" in compount version requirements, it's meaningless.
p5-EV: update to 4.37.
4.37 Thu 22 Jan 2026 16:05:45 CET
- so ExtUtils::ParseXS is a mess. Installing the latest CPAN
version works, but the version in Perl 5.42 does not. That is,
fedora 43 fails, debian's 5.42 works. I've tried to work around
it again. Thanks to vividsnow for alerting me to this.
4.36 Fri 19 Sep 2025 19:15:30 CEST
- seems the xsubpp maintainer changes syntax every few releases.
use extremely ugly workaround. goddamnit.
