Date: Sat, 24 Jan 2009 18:57:26 +0100 From: Pojken Purken <pp@pp.dyndns.biz> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: default CFLAGS Message-ID: <497B5686.8050600@pp.dyndns.biz> In-Reply-To: <20090124174357.4aafcf1a@gumby.homeunix.com> References: <Pine.LNX.4.64.0901241734020.6296@localhost> <20090124124535.3006687c@gumby.homeunix.com> <9a52b1190901240451i14dc544fm1c241d6f43fa897b@mail.gmail.com> <20090124131629.1f9fabe4@gumby.homeunix.com> <497B2536.7030907@pp.dyndns.biz> <20090124174357.4aafcf1a@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
RW wrote: > On Sat, 24 Jan 2009 15:27:02 +0100 > Morgan Wesström <freebsd-questions@pp.dyndns.biz> wrote: > > >> The section "options enabled" will list them all. I usually only add >> "-march=native" to my CFLAGS to enable a few more CPU specific >> optimizations. > > If you set CPUTYPE, -march is set to match, so setting -march=native > should be redundant. OTOH a number of other make variables are defined > from CPUTYPE, so if you set -march=native, but not CPUTYPE you might > miss some optimisations based on build options. > > I've no idea whether there are any such options, just that you're > probably not going to do better than setting CPUTYPE, and leaving the > rest alone. I'm sorry I was unclear. I set CPUTYPE to native of course which is then passed as -march=native to compiler.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?497B5686.8050600>