My sick CFLAGS will take on your ASSembly cireclejerk anyday. Don't be shy, come up with your best optimizations. Oh wait, you don't have CFLAGS right? More like ASSFAGS right?
Aye carumba! Are you absolutely sure you've got enough CFLAGS in there? How
about adding -O3 and -ffastmath in there for good measure...?
Seriously, the root of your problems here, is the insane CFLAGS you have set.
Just because a certain flag is recognised by GCC, doesn't mean it's necessarily
a good idea to go playing with it, unless you're familiar with what it does, and
what the consequences are.
Likely, due to the abuse of these flags, your system is most likely messed up
beyond all repair. (FUBAR, as some of my mates would call it... I'll leave it
to others to derive the definition of that acronym)
Might I suggest, trimming back on the CFLAGS (e.g. I'd recommend "-O2 -pipe
-march=athlon-xp" and leave it at that) and see how that goes. You may also
need to rebuild glibc and other components of your system -- so it may be easier
to reformat and reload.
The performance gained by CFLAGS on x86 is minimal at best -- largely because
the machines are still basically overclocked 386's at their core. RISC
architectures (e.g. MIPS) can benefit by compiling to a particular ISA and CPU,
(e.g. throwing in -mips4 on an SGI O2 will get it humming nicely) however, going
beyond that only causes major headaches.
In short though, the only thing gained by lots of CFLAGS is über instability,
horrendous compile errors, and next to no speed gain.Aye carumba! Are you
absolutely sure you've got enough CFLAGS in there? How about adding -O3 and
-ffastmath in there for good measure...?
Seriously, the root of your problems here, is the insane CFLAGS you have set.
Just because a certain flag is recognised by GCC, doesn't mean it's necessarily
a good idea to go playing with it, unless you're familiar with what it does, and
what the consequences are.
Likely, due to the abuse of these flags, your system is most likely messed up
beyond all repair. (FUBAR, as some of my mates would call it... I'll leave it
to others to derive the definition of that acronym)
Might I suggest, trimming back on the CFLAGS (e.g. I'd recommend "-O2 -pipe
-march=athlon-xp" and leave it at that) and see how that goes. You may also
need to rebuild glibc and other components of your system -- so it may be easier
to reformat and reload.
The performance gained by CFLAGS on x86 is minimal at best -- largely because
the machines are still basically overclocked 386's at their core. RISC
architectures (e.g. MIPS) can benefit by compiling to a particular ISA and CPU,
(e.g. throwing in -mips4 on an SGI O2 will get it humming nicely) however, going
beyond that only causes major headaches.
In short though, the only thing gained by lots of CFLAGS is über instability,
horrendous compile errors, and next to no speed gain.