From owner-freebsd-current@FreeBSD.ORG Mon Mar 7 22:45:31 2011 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 04B231065673; Mon, 7 Mar 2011 22:45:31 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9F6D78FC12; Mon, 7 Mar 2011 22:45:30 +0000 (UTC) Received: by ywf9 with SMTP id 9so2039776ywf.13 for ; Mon, 07 Mar 2011 14:45:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DKMbNjGUcvShqvOchnpw5p6ECedFxip9BtcF6z05TAM=; b=naonw6Jzhas57FxxKdKgihzXuDpm7y3uWCc79+mBjwOnQlDfyZ19OrX1tt4OjQvtcM JZoM7MZOtE0QQ3jouweI0l93eSl3HW6KJFrOayKnOmx9MyhYNQS1lAd/8q1y0owcVgeq soSHxIvK7I0Qu1gMzVIXQpnNyb7GyTOvGIC10= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=C6quTT5LJr9lhZBosMBqPEBe+SrqmpW1MMrl2wyLSGSFWehE+wB4niMIc+GGApKPKQ Vi01wcYYfnjEh/oEuCdTnEU5rwTIYLfRm3krLXveHPK+MPzmQj91ZD2iAJc5uoCPnrcH o0EmeUz9qU4ZqWs7UJS8dxWrOak2K7PhQkOYU= MIME-Version: 1.0 Received: by 10.100.19.8 with SMTP id 8mr1526906ans.88.1299537929484; Mon, 07 Mar 2011 14:45:29 -0800 (PST) Received: by 10.100.106.15 with HTTP; Mon, 7 Mar 2011 14:45:29 -0800 (PST) In-Reply-To: <20110307214935.GA53914@freebsd.org> References: <20110307205957.GA47557@freebsd.org> <20110307214935.GA53914@freebsd.org> Date: Tue, 8 Mar 2011 00:45:29 +0200 Message-ID: From: George Liaskos To: Alexander Best Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org Subject: Re: r219385 build error. 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: Mon, 07 Mar 2011 22:45:31 -0000 > either "native" or "nocona" (actually native should evaluate to nocona): > > touch _native_test.c && gcc -march=native -### _native_test.c > > should tell which -march and -mtune settings gcc assumes for "native". > > indeed there are some known problems with "native", but i think those are > limited to architectures such as mips and arm. with i386 or amd64 "native" > shouldn't cause any problems. > > i think core2 was always wrong to set in make.conf, because the base gcc simply > does not support it. however so many people are trying to boost speed etc. by > adding make.conf options they find scattered over the internet and on various > linux dist wikis, that core2 was added as a workaround so people could use it > (even though it wasn't supported). I still don't understand how bsd.cpu.mk is going to handle "native" as value to set CPUTYPE / MACHINE_CPU, or this is irrelevant? Would it be better to use the following? CPUTYPE?=nocona NO_CPU_CFLAGS=yes NO_CPU_COPTFLAGS=yes CFLAGS+= -march=native Thank you for your clarifications.