> It does, but will this affect that? Does gcc change the CPU arch to 32bit era
> hardware when using -m32?
I did some quick testing with this, normally only __i386__ gets
defined for 32 bit builds (-march=native -m32 for example, but also
the default -march=x86-64 -m32). __i586__ and __i686__ are only there
if I pass the matching -march (i586/i686) flag to gcc.