Date: Sat, 08 Oct 2005 22:03:00 -0700 From: ray@redshift.com To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-amd64@freebsd.org Subject: Re: /etc/make.conf Message-ID: <3.0.1.32.20051008220300.00a74ba8@pop.redshift.com> In-Reply-To: <20051009045843.GA93028@xor.obsecurity.org> References: <3.0.1.32.20051008215252.00a74ba8@pop.redshift.com> <3.0.1.32.20051008202606.00a74ba8@pop.redshift.com> <3.0.1.32.20051008202606.00a74ba8@pop.redshift.com> <3.0.1.32.20051008215252.00a74ba8@pop.redshift.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:58 AM 10/9/2005 -0400, Kris Kennaway wrote: | On Sat, Oct 08, 2005 at 09:52:52PM -0700, ray@redshift.com wrote: | > At 11:53 PM 10/8/2005 -0400, Kris Kennaway wrote: | > | On Sat, Oct 08, 2005 at 08:26:06PM -0700, ray@redshift.com wrote: | > | > Hi, | > | > | > | > anyone have any settings for CPUTYPE and CFALGS in /etc/make.conf when | > running | > | > AMD64 5.4-release on a dual AMD Opteron server? I'm moving over from i386, so | > | > just want to make sure I get the right stuff in there before compiling | > | > everything. I'm thinking something along these lines: | > | > | > | > CPUTYPE=k8 | > | > CFLAGS=-O2 -pipe -funroll-loops march=k8 | > | | > | Don't try to use elite home-grown CFLAGS unless you know precisely | > | what you're doing. Just set CPUTYPE and use the default CFLAGS. | > | | > | Kris | > | | > | Attachment Converted: "c:\eudora2\ATTACH\Re etcmake.conf" | > | | > | > I set CPUTYPE=opteron and CFLAGS=-O2 -pipe -funroll-loops | > | > seems to be working well. Thanks! | | OK, so you chose to ignore my advice. When you run into problems, | please remember not to report them before reverting to the default | CFLAGS setting. | | Kris | | | Attachment Converted: "c:\eudora2\ATTACH\Re etcmake1.con" | I've been running those flags for years - if you would like to supply some logic as to why they won't work on the AMD platform, then maybe that would help. If your advice is just "don't do that, it's bad", then doesn't help much. -O2 has always worked fine for our production servers. What flag specifically are you nervous about? Ray
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.1.32.20051008220300.00a74ba8>