Which optimization for x86-64
Dennis Veatch
dveatch at woh.rr.com
Fri May 13 16:28:32 UTC 2005
On Friday 13 May 2005 10:39 am, Jon South wrote:
> Dennis Veatch wrote:
> > On Friday 13 May 2005 10:14 am, Jon South wrote:
> >>Dennis Veatch wrote:
> >>>On Friday 13 May 2005 9:10 am, Moritz Heiber wrote:
> >>>>On Fri, 13 May 2005 08:34:31 -0400
> >>>>
> >>>>Dennis Veatch <dveatch at woh.rr.com> wrote:
> >>>>>Ok, tried that and relined gcc. The lin failed before it got to the
> >>>>>point of recompiling gcc with "badvalue (athon64) for march and mcpu".
> >>>>
> >>>>It should be 'Athlon64' or 'athlon64' .. not athon64.
> >>>>
> >>>>Regards,
> >>>>
> >>>>Moritz
> >>
> >>It should also be noted that by using those opts, it's still only going
> >>to be 32 bit. To force compiling 64 bit requires -m64 -- but that wont
> >>do you any good with a 32 bit kernel... At the moment, it's not worth
> >>the effort to try and compile 64 bit apps until we get a 64 bit ISO
> >>going for it, and even then, it will take some effort to create and to
> >>maintain.
> >>
> >>-Striker
> >
> > Where in the optimizations would I insert "-m64"?
>
> Nowhere unless you really want a non-working system. 64 bit is
> unsupported, and I have no intention of helping you break your system.
> You need to research how 64bit is actually implemented and assess
> whether you can actually do it on your system. There are many apps that
> will not work in a 64bit environment; and you can't just 'jump' to 64bit
> when your system was compiled as 32bit already.
>
> -Striker
I'm not concerned about breaking my system, it's just a machine.
More information about the Lunar
mailing list