From owner-freebsd-current@FreeBSD.ORG Thu Jul 9 08:50:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FAE81065673; Thu, 9 Jul 2009 08:50:26 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id D87718FC14; Thu, 9 Jul 2009 08:50:25 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from seis.bris.ac.uk ([137.222.10.93]) by dirg.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1MOpKb-0007gO-2V; Thu, 09 Jul 2009 09:50:25 +0100 Received: from mech-cluster238.men.bris.ac.uk ([137.222.187.238]) by seis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1MOpKa-0007mW-8s; Thu, 09 Jul 2009 09:50:16 +0100 Received: from mech-cluster238.men.bris.ac.uk (localhost.men.bris.ac.uk [127.0.0.1]) by mech-cluster238.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id n698oFMw043408; Thu, 9 Jul 2009 09:50:15 +0100 (BST) (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster238.men.bris.ac.uk (8.14.3/8.14.3/Submit) id n698oFLl043407; Thu, 9 Jul 2009 09:50:15 +0100 (BST) (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster238.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Thu, 9 Jul 2009 09:50:15 +0100 From: Anton Shterenlikht To: Marcel Moolenaar Message-ID: <20090709085014.GE43264@mech-cluster238.men.bris.ac.uk> References: <20090707094808.GA93317@mech-cluster238.men.bris.ac.uk> <20090707095058.GC7827@rink.nu> <20090707124405.GA46091@mech-cluster238.men.bris.ac.uk> <20090707133611.GA66072@rink.nu> <93B562A8-9FE7-44D5-91E4-C9AB1A25BD2A@mac.com> <20090708114019.GA19781@mech-cluster238.men.bris.ac.uk> <650DC54B-5FA6-49CB-8A9C-58461289778F@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <650DC54B-5FA6-49CB-8A9C-58461289778F@mac.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -1.5 X-Spam-Level: - Cc: Rink Springer , Anton Shterenlikht , freebsd-current@freebsd.org, freebsd-ia64@freebsd.org Subject: Re: buildworld panic on ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jul 2009 08:50:26 -0000 On Wed, Jul 08, 2009 at 09:19:33AM -0700, Marcel Moolenaar wrote: > > On Jul 8, 2009, at 4:40 AM, Anton Shterenlikht wrote: > > >> BTW: I never got the error when doing a buildworld. I > >> think Anton's non-standard compiler options make GCC much > >> more FP intensive and thus prone to causing the race. > > > > hey, my compiler options are just a copy from > > /usr/share/examples/etc/make.conf > > > > with obvious changes, e.g. CPUTYPE=itanium2 > > The CFLAGS, COPTFLAGS, CXXFLAGS are as in the example make.conf. > > > > Which non-standard options did you spot? > > All of them :-) > > There is no /etc/make.conf by default, so the existence > of /etc/make.conf with CFLAGS, COPTFLAGS, etc makes them > non-standard. > > As a special warning: /usr/share/examples/etc/make.conf > is inherently i386 biases (like most of the examples and > documentation I might add). It's unwise to copy flags > from there and expect good results. Even warnings-only > examples can cause build breakages (due to -Werror), > because compilers for different architectures emit > different warnings or emit the same warning at different > times. > > By all means: experiment. But be very careful not to make > the assumption that if the code compiles, it'll also run. > The weirder the set of compiler options, the more likely > you trip over optimization bugs and end up with an unstable > system. And I'm not even talking about whether the set > of options give you more optimal code in general. I see.. Is there any advice for compiler options on ia64? Perhaps a sample make.conf for ia64? Or would you recommend leaving these options empty: CFLAGS, COPTFLAGS, CXXFLAGS ? I'm sorry if I'm asking obvious questions. Perhaps this is documented/disucced somewhere already? I'm new to ia64, most of my FBSD experience is from alpha and i386. many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423