3 ms·
> (2) 386 complicates code paths for 32-bit x86, which people still care about (even if only a little) for real world production use. I don't know how much of
by zozbot234 6y ago
> (2) 386 complicates code paths for 32-bit x86, which people still care about (even if only a little) for real world production use.
I don't know how much of a concern this is IRL, given that one could hide essentially all 386-specific workarounds behind #ifdef's.
- innocenat 6y ago386 specific workaround code still needed to be updated if relevant part of the code is updated. If you look at the patch the remove 386 support (http://lkml.iu.edu/hypermail/linux/kernel/1212.1/01152.html http://lkml.iu.edu/hypermail/linux/kernel/1212.1/01152.html), you can already see that it's already under #ifdef. There are quite a number of atomic instructions not available for 386 which all requires workaround.
- zozbot234 6y agoLooks like that code could have been refactored to be better self-contained. Though I suppose removing it altogether is a fine way to go about it; it can always be reintroduced in the future if folks commit to maintaining the support going forward.