Date: Sun, 10 Feb 2013 08:44:24 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Boris Samorodov <bsam@passap.ru> Cc: freebsd-current@freebsd.org Subject: Re: 7+ days of dogfood Message-ID: <20130210164424.GA77092@troutmask.apl.washington.edu> In-Reply-To: <5117A319.60804@passap.ru> References: <20130210000723.GA73630@troutmask.apl.washington.edu> <5117A319.60804@passap.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 10, 2013 at 05:39:37PM +0400, Boris Samorodov wrote: > 10.02.2013 04:07, Steve Kargl ??????????: > > As for me I use CURRENT at my JOB for many years now. > I used to i386 but switched to amd64 at the end of 2012. > The system (both world and kernel) are updated every > week or two. > My workstation at work is amd64 and I have a 20 node amd64 cluster. All of these systems run freebsd-current. I've only had a few problems when building ports. > > One option that I use has been already mentioned -- MALLOC_PRODUCTION. > > > CPUTYPE?=core2 > > I never use this option. It was very long ago that I was > beaten by it, but don't like it since. Without it, the build infrastructure was selecting -march=i486, which produced even worse results. Several ports would not compile because llvm's integrated assembler was given invalid assembly constructs. > > FFLAGS = -O2 -pipe -march=native -mtune=native > > I don't like using "=" for FLAGS at make.conf... > > > FFLAGS+= -funroll-loops -ftree-vectorize > > ... as well as defaults overriding. > FFLAGS are the options used while compiling Fortran. Having spent years contributing to and testing gfortran, I am fairly comfortable with these options. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130210164424.GA77092>