From owner-freebsd-toolchain@FreeBSD.ORG  Wed May 29 16:06:47 2013
Return-Path: <owner-freebsd-toolchain@FreeBSD.ORG>
Delivered-To: toolchain@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 0CAEE53D
 for <toolchain@freebsd.org>; Wed, 29 May 2013 16:06:47 +0000 (UTC)
 (envelope-from imp@bsdimp.com)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com
 [IPv6:2607:f8b0:4003:c01::229])
 by mx1.freebsd.org (Postfix) with ESMTP id C9791686
 for <toolchain@freebsd.org>; Wed, 29 May 2013 16:06:46 +0000 (UTC)
Received: by mail-ob0-f169.google.com with SMTP id up14so4203505obb.28
 for <toolchain@freebsd.org>; Wed, 29 May 2013 09:06:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=google.com; s=20120113;
 h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to:x-mailer
 :x-gm-message-state;
 bh=KQfJZcCTovTv3LoyiUc8IpdEJ0fUljqZMYMIToPGUeo=;
 b=VOIGcmoCy4tA7ZrUCKQNa1KaM6+vNBJ0k1hZCbNv8xNUdp8jKDVhxa3uDK0aA2hpB8
 DF7b09mk9iGb07cONF7g4BVWL/a1uVOmLyxeGYvA/9Q1FXtJxUtzJJZnJm00uFgPqUPc
 1e7ZMf+B3BNGFCys9XFFYPgz7o1hLpPAjlwOFwQmnktsNL1EEL+k/hWgWcuHZZ+Rsst/
 +7LLM1bUDPxUVlZtkZso28ghV5NvgtV9P37BGyGhDYWH9BUowuINC616k/TDFtauEnyB
 YhchBLEL4+T3EPWw0K0VAxBKpf3thuLZUbY9AekLB0gi5XRtuEZ8lNIHBtSVDy/A3toF
 7UTA==
X-Received: by 10.60.34.135 with SMTP id z7mr2051708oei.68.1369843606284;
 Wed, 29 May 2013 09:06:46 -0700 (PDT)
Received: from monkey-bot.int.fusionio.com ([209.117.142.2])
 by mx.google.com with ESMTPSA id sa2sm11157904oeb.1.2013.05.29.09.06.44
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 29 May 2013 09:06:45 -0700 (PDT)
Sender: Warner Losh <wlosh@bsdimp.com>
Subject: Re: [CFT] gcc: support for barcelona
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <C0B4C633-EC1C-41AF-BE57-76B52DF47F52@FreeBSD.org>
Date: Wed, 29 May 2013 10:06:40 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <65AA3A88-7B5E-439F-950D-47EDCDC3EAD1@bsdimp.com>
References: <51A38CBD.6000702@FreeBSD.org>
 <E9DC99EF-F2E9-4A5F-8370-36DA25DE2C89@felyko.com>
 <51A3B8AB.5080808@FreeBSD.org>
 <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com>
 <3C29AD82-077D-4E6B-94C7-5D069A130348__27528.1591726982$1369769859$gmane$org@FreeBSD.org>
 <51A5A6F4.8000501@FreeBSD.org>
 <C0B4C633-EC1C-41AF-BE57-76B52DF47F52@FreeBSD.org>
To: David Chisnall <theraven@FreeBSD.org>
X-Mailer: Apple Mail (2.1085)
X-Gm-Message-State: ALoCoQmF/C+NzpoGa5YtOw3IeuyezqkTemDmAl3HkgYpp7zZcuZ2AUr7TvpiuRvcnXmgZ6vnpNtA
Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Pedro Giffuni <pfg@FreeBSD.org>,
 Rui Paulo <rpaulo@felyko.com>, Andriy Gapon <avg@FreeBSD.org>
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 16:06:47 -0000


On May 29, 2013, at 2:47 AM, David Chisnall wrote:

> On 29 May 2013, at 07:57, Andriy Gapon <avg@FreeBSD.org> wrote:
>=20
>> In fact, I am of opinion that while such bugs exist gcc should be =
crowned back
>> as a default compiler.
>=20
> Seriously?  Your show stopper bug is that, very occasionally, clang =
emits incorrect debug info?  And Steve's is that clang emits code that =
is fully compliant with the C standard, but gives more floating point =
precision than he wanted?
>=20
> If those are the most serious problems we have with clang, then it's =
time to remove gcc 4.2.1 from the tree right now.  I wish the problems =
that we had with it were so trivial...

NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO =
.
There are serious problems with clang on arm right now. And it doesn't =
support mips. Removing gcc is way premature.

Warner