Re: Compiler opt

To: debian-amd64@lists.debian.org
Subject: Re: Compiler opt
From: Karl Hegbloom <hegbloom@pdx.edu>
Date: Sat, 28 Aug 2004 11:55:04 -0700
Message-id: <[🔎] 1093719304.15893.21.camel@localhost>
In-reply-to: <[🔎] 1093687894.2455.3.camel@localhost.localdomain>
References: <[🔎] 1093652533.724.16.camel@cathcart.sysc.pdx.edu> <[🔎] 1093687894.2455.3.camel@localhost.localdomain>

On Sat, 2004-08-28 at 12:11 +0200, Sebastian Steinlechner wrote:
> On Sat, 2004-08-28 at 02:22, Karl Hegbloom wrote:
> > How do I determine the default compiler optimization settings?  I'm
> > wonder if it will be worth while to try and recompile things like
> > python2.3 and python2.3-numeric with '-m64'?  Or is '-m64' already the
> > default?
> 
> If you're compiling on pure64, then you'll get 64-bit ELFs/libs (so -m64
> is the default).

Ok.  So then -m64 implies -march=k8 ?

-- 
    Karl Hegbloom
(o_  mailto:hegbloom@pdx.edu
//\   jabber:karlheg@jabber.org
V_/_   yahoo:karlheg

Reply to:

Follow-Ups:
- Re: Compiler opt
  - From: Ron Johnson <ron.l.johnson@cox.net>
- Re: Compiler opt
  - From: Paul Brook <paul@codesourcery.com>

References:
- Compiler opt
  - From: Karl Hegbloom <hegbloom@pdx.edu>
- Re: Compiler opt
  - From: Sebastian Steinlechner <amd64@resourcecode.de>

Prev by Date: Re: installation stuck in loop
Next by Date: Re: Compiler opt
Previous by thread: Re: Compiler opt
Next by thread: Re: Compiler opt
Index(es):
- Date
- Thread