Your recommendation fixed my problem, thank you for your insistence. I think i had selected "-mtune" for if ever my motherboard fails and i have to replace it, to end up with possibly another processor, then hopefully i would have a system which runs, thanks to the generic parts of the code. So, i guess you can't win them all, now i'll have to stick with "-march". I had also conducted some research on the "undefined reference to `__sync_add_and_fetch_4'" symptom, but failed to locate that page you indicate. Thanks again.
On Fri, Feb 13, 2009 at 11:42 AM, Ian Lee <[email protected]>wrote: > Jerome Potts wrote: > >> i have "-mtune=athlon". Back when i set this up, "mtune" was preferable to >> "march". But they are quite similar. And i've had it this way for quite a >> long time, and i've never had any reason to change it, and i've never had >> this problem. >> >> >> On Thu, Feb 12, 2009 at 4:16 PM, Ian Lee <[email protected]<mailto: >> [email protected]>> wrote: >> >> >> Try putting -march=athlon in your CFLAGS. >> >> >> ------------------------------------------------------------------------ >> >> > A quote from http://www.gentoo.org/doc/en/gcc-optimization.xml > > " > On x86 and x86-64 CPUs, -march will generate code specifically for that CPU > using all its available instruction sets and the correct ABI; it will have > no backwards compatibility for older/different CPUs. If you don't need to > execute code on anything other than the system you're running Gentoo on, > continue to use -march. You should only consider using -mtune when you need > to generate code for older CPUs such as i386 and i486. -mtune produces more > generic code than -march; though it will tune code for a certain CPU, it > doesn't take into account available instruction sets and ABI. Don't use > -mcpu on x86 or x86-64 systems, as it is deprecated for those arches." > > A quote from the gcc man page > > " There is no -march=generic option because -march indicates the > instruction set the compiler can use, and there is no generic instruction > set applicable to all processors. In contrast, -mtune indicates the > processor (or, in this case, collection of processors) for which the code is > optimized. " > > Similar problem on this page > > http://stackoverflow.com/questions/130740/link-error-when-compiling-gcc-atomic-operation-in-32-bit-mode > > They maybe similar but the difference seems to be significant in this > instance, maybe now you have a reason to change it. >
_______________________________________________ paludis-user mailing list [email protected] http://lists.pioto.org/mailman/listinfo/paludis-user
