Or x32-hosted, i486-targeting if I want the resulting cross compiler binaries to be more universal.
-
-
-
@RichFelker I've found i686 to be plenty. That's Pentium II, which was introduced 19 years ago.
End of conversation
New conversation -
-
-
@RichFelker I only think about i786 these days. Noticed compilers don't even emit x87 FPU code anymore (silly FPU stack). It's all SSE. -
@mjcmeta For 32-bit x86 the x87 regs are part of the ABI, so compilers have to, short of replacing the ABI.
-
@mjcmeta And replacing the ABI for an arch that's largely replaced already is not what most ppl consider a good use of effort.
-
@mjcmeta In any case, the details don't matter; all that matters for making GCC builds faster/less-mem-hogging is using 32-bit pointers.
End of conversation
New conversation -
-
-
@RichFelker I use i686 as the host compiler for my cross compilers for the same reason.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@RichFelker still had some machines without NX running in 2008. The thought scares me.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@RichFelker non executable stack is also what I would call an essential feature these days. NX circa ~2005Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@RichFelker core i7 Nehalem onwards. That's like ~2008. ~7 yrs old hardware.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.