Search results

** An ABI-compliant <code>-fstack-clash-protection</code> implementation has not yet ...

The following packages must be rebuilt: N/A. This time there is no API/ABi change in NIF or Driver API. ...

...m.com/help/topic/com.arm.doc.ihi0042d/IHI0042D_aapcs.pdf AAPCS]. The newer ABI (as defined in section 6 of the AAPCS) uses floating point registers as par ...double floating point registers and they are not required for base hardfp ABI compatibility. We will build for a Cortex-A8 optimized target, not requirin ...

The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is one of explicit Boost non-goals, this entails rebuilding of al ...

The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is one of explicit Boost non-goals, this entails rebuilding of al ...

The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is absent from Boost, this entails rebuilding of all dependent pa ...

I checked the ABI compatiblity and the report can be found here:<br> ...

...y file that's in a package payload, generating a bytecode file for the 2.6 ABI. * the magic ABI value stored in the .pyc/.pyo file needs to match that of the python binary ...

...) against Erlang 19.x.y. THis time Erlang uses the same Driver version API/ABI as in a previous release so driver libraries rebuild isn't necessary</s>. D ...

...ebuild (if required) before the final release of glibc 2.36, but after the ABI is frozen. ...ar, but to do so may require a mass rebuild to remove new symbols from the ABI/API. ...

|Canaletto|| Tuesday ||16:30 ||Ensuring ABI stability in Fedora || hguemar || TBD ...

...ar, but to do so may require a mass rebuild to remove new symbols from the ABI/API. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> * Contingency deadline: Upstream glibc ABI freeze deadline of 2021-07-01. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> ...

...ebuild (if required) before the final release of glibc 2.37, but after the ABI is frozen. ...ar, but to do so may require a mass rebuild to remove new symbols from the ABI/API. ...

...le point release for a longer amount of time. Red Hat also aims to provide ABI compatibility within a release, whereas this is not guaranteed by the Fedor ...

We're not removing any functionality and keeping the ABI in place (though we add new libraries). The upgrades should be seamless. ...

...rebuild (if required) before the final release of glibc X.Y, but after the ABI is frozen. ...ar, but to do so may require a mass rebuild to remove new symbols from the ABI/API. ...

...e the object files in the static library. The GNU C Library only provides ABI compatibility with dynamic linking; all static libraries have to be recompi ...

...ebuild (if required) before the final release of glibc 2.40, but after the ABI is frozen. ...ar, but to do so may require a mass rebuild to remove new symbols from the ABI/API. ...

...loating-point arguments directly in FPU registers. This is an incompatible ABI change, so programs which pass value in the CPU registers are incompatible ...

...build dynamic link libraries at this time due to the lack of a stabilized ABI for Rust. ...