From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 23:46:13 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 519E6D0 for ; Sat, 3 Nov 2012 23:46:13 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id 09A878FC08 for ; Sat, 3 Nov 2012 23:46:12 +0000 (UTC) Received: from [192.168.0.6] (spaceball.home.andric.com [192.168.0.6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 0B99D5C59; Sun, 4 Nov 2012 00:46:12 +0100 (CET) Message-ID: <5095ACC7.1050002@FreeBSD.org> Date: Sun, 04 Nov 2012 00:46:15 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Alexander Leidinger Subject: Re: Do we have a CPUTYPE=native and/or generic stability problem? References: <20121103232433.00005eee@unknown> In-Reply-To: <20121103232433.00005eee@unknown> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 03 Nov 2012 23:46:13 -0000 On 2012-11-03 23:24, Alexander Leidinger wrote: > while trying to update from r239708 to r242511 (amd64 arch) I tried to > compile the world with "make -j8". After a short while I got an > internal error in the clang compile (this is a gcc-compiled system, I > don't use clang). The CFLAGS/COPTFLAGS are -O2 -pipe. > > Without the -j8 it compiles just fine. > Without the CPUTYPE?=native it compiles even with -j8. Hm, at first I thought you might be running out of RAM, but apparently that is not the case then. :) > The CPU is an Intel(R) Xeon(R) CPU (L5630) with ECC ram. What does gcc detect for this CPU with -march=native? You can do: gcc -march=native -v -c -x c /dev/null 2>&1 | grep -- -march to see what it passes to the second stage. > The r239708 world runs stable since I installed it (build with > CPUTYPE=native). The r242511 world (no CPUTYPE set) doesn't run stable > (not only the watchdogd segfault I reported in another mail some minutes > ago, but also some other kind of reboot every X minutes I haven't > investigated yet). > > Does someone run -current on a similar system on a similar revision and > can comment about the stability? I run r242303 on both i386 and amd64, no instability whatsoever. But I compile everything with clang, and an explicit CPU type for the processor in use, so my case is not comparable to yours, unfortunately.