Jan-Benedict Glaw wrote:
>Please apply. Worst to say, even Debian seems to start using i486+
>features (ie. libstdc++5 is SIGILLed on Am386 because there's no
>"lock" insn available)...
g++ >=3.2 use 486-specific instructions in order to do atomic operations
in C++ code. 3.3 includes a 386 version of the same code, but it's not
possible to use a mixture of the two (ie, code compiled with a "486" g++
will not work on the "386" version), and so to keep ABI compatibility
with the other distributions it's necessary to break 386. The "obvious"
solution (dragging this back on topic) is a kernel patch to emulate 486
instructions on a 386.
-- Matthew Garrett | mjg59-chiark.mail.linux-rutgers.kernel@srcf.ucam.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:46 EST