On Fri, Aug 22, 2008 at 11:05:12AM -0700, H.J. Lu wrote: > On Fri, Aug 22, 2008 at 10:53 AM, Sebastian Redl > <[EMAIL PROTECTED]> wrote: > > H.J. Lu wrote: > >> > >> Can we declare that Linux/ia32 generates i486 insn by default? > >> > > > > Even if we do that, we'll still get errors if someone forces i386. And the > > people doing that are more likely to want to link against the standalone > > libsupc++, too, since i386 is mostly used in embedded systems nowadays. > > > > Can we disable those new C++ features for i386? Do embedded systems > use/need those new C++ features?
People are putting everything on embedded systems these days, including things like Qt-based GUIs, threaded apps that need locking, the works. And some embedded processors might support only i386 instructions. Certainly we could default to i486, but we can't wish the i386 problems away.