#abibreak — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #abibreak, aggregated by home.social.
-
Since Intel's #GraniteRapids identifies as Family 19, does that mean we're looking at i1986 (after 3 decades of i686)?
Obviously i686/amd64 binaries will continue to work, but i1986 binaries won't work at all on older systems. (Current ISA extensions can often be used behind ifunc dispatch - but APX wants to affect *everything*.)
This seems like a perfect opportunity for an #ABI break, no? -
Since Intel's #GraniteRapids identifies as Family 19, does that mean we're looking at i1986 (after 3 decades of i686)?
Obviously i686/amd64 binaries will continue to work, but i1986 binaries won't work at all on older systems. (Current ISA extensions can often be used behind ifunc dispatch - but APX wants to affect *everything*.)
This seems like a perfect opportunity for an #ABI break, no? -
Since Intel's #GraniteRapids identifies as Family 19, does that mean we're looking at i1986 (after 3 decades of i686)?
Obviously i686/amd64 binaries will continue to work, but i1986 binaries won't work at all on older systems. (Current ISA extensions can often be used behind ifunc dispatch - but APX wants to affect *everything*.)
This seems like a perfect opportunity for an #ABI break, no? -
Since Intel's #GraniteRapids identifies as Family 19, does that mean we're looking at i1986 (after 3 decades of i686)?
Obviously i686/amd64 binaries will continue to work, but i1986 binaries won't work at all on older systems. (Current ISA extensions can often be used behind ifunc dispatch - but APX wants to affect *everything*.)
This seems like a perfect opportunity for an #ABI break, no?