From owner-freebsd-toolchain@FreeBSD.ORG Tue May 28 17:41:50 2013 Return-Path: <owner-freebsd-toolchain@FreeBSD.ORG> Delivered-To: freebsd-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 45DEEF30 for <freebsd-toolchain@freebsd.org>; Tue, 28 May 2013 17:41:50 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-oa0-f51.google.com (mail-oa0-f51.google.com [209.85.219.51]) by mx1.freebsd.org (Postfix) with ESMTP id 123C9AC5 for <freebsd-toolchain@freebsd.org>; Tue, 28 May 2013 17:41:49 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id f4so10337603oah.38 for <freebsd-toolchain@freebsd.org>; Tue, 28 May 2013 10:41:49 -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=DLt2ZZDq/oR3efeBTGzm3kNmpkMd4lfy4N2N+D5uBxE=; b=Qf0YhG6sY5iGSFA9/9trUTV3+qyiAt3wWUCf3h740IuXMAfN2MugBHObd5PSd896Ac swjgW0qvAYanPi38U92QBmwdlZKNgAclvELlXRCassVuJi9vzSe8aZ+eeC/GV5rICIGG GnwNRoB1WiDAnyD3KQrh8iu8Rn4FoC9gzCZ3NZlXLdaJHSgO6zdcBG0aB2ZzTEz1OrA7 KFssXWjcM5N/FqmEfznLZ1BnitFYKDs4+mR/lKE/vxrsT2g+Q8W5zIWuYPgHvizHANfN drNdIoGrTyh8R7nvqTtt3TSKhXjBw4bFiEbgKbZ6EldbadrBAmueblScTUw8I5uZTDVQ 7fWA== X-Received: by 10.182.108.194 with SMTP id hm2mr1652692obb.71.1369762909545; Tue, 28 May 2013 10:41:49 -0700 (PDT) Received: from monkey-bot.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id hv3sm35667287obb.7.2013.05.28.10.41.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 10:41:48 -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: <51A3BCF4.1010008@FreeBSD.org> Date: Tue, 28 May 2013 11:41:47 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <FCD093B4-9056-4250-83E4-3FE60FF49699@bsdimp.com> References: <51A38CBD.6000702@FreeBSD.org> <E9DC99EF-F2E9-4A5F-8370-36DA25DE2C89@felyko.com> <4BD4D414-8281-4127-A520-565CF28FF5E5@FreeBSD.org> <51A3BCF4.1010008@FreeBSD.org> To: Pedro Giffuni <pfg@FreeBSD.org> X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQkn6APh/h/511c7uiXwjOhU1ZRSvXCjbU5OF/tXwrIFXAnXxynu7fSQKJnCXiYgZXqFuluw Cc: freebsd-toolchain@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: Tue, 28 May 2013 17:41:50 -0000 On May 27, 2013, at 2:07 PM, Pedro Giffuni wrote: > On 27.05.2013 14:38, Dimitry Andric wrote: >> On May 27, 2013, at 21:12, Rui Paulo <rpaulo@felyko.com> wrote: >>> On 27 May 2013, at 09:41, Pedro Giffuni <pfg@freebsd.org> wrote: >>>> Almost a year ago I tried to bring in the support for AMD's = barcelona >>>> chipset into our gcc. This actually filled a lot of holes in that = were left >>>> when similar intel support was brought in. >>>>=20 >>>> Unfortunately I had to revert rapidly such support as it broke = building >>>> some C++ ports even when it was not being used. >>>>=20 >>>> jkim@ did some cleanup of the support and the patch has been >>>> gathering rust here: >>>>=20 >>>> http://people.freebsd.org/~jkim/reworked-r236962-3.diff >>>>=20 >>>> The patch still applies cleanly and there is a good chance it will = work >>>> since there have been other fixes merged since the last time. >>>>=20 >>>> I did some basic testing and so far it works for me but I don't = have >>>> the specific chipset. Additional testing would be welcome. >>> I have to question the general direction of this work. We switched = to Clang as the default compiler for i386/amd64 some months ago and now = you're working on improving our base GCC especially for amd64? I don't = really understand how useful this is. It doesn't strike me as a good = idea to see people working on things that will eventually be replaced / = removed. >> It is probably a better use of time to work on getting the tree to = build >> with an out-of-tree gcc 4.7 or 4.8 instead. Why spend more effort on = a >> completely dead branch of gcc? Newer gcc's have better code = generation, >> support for more modern CPUs, and better diagnostics (including even >> those controversial carets ;-). >=20 > FWIW, upstream gcc has a bug that affects ctfmerge and they have > been very slow to fix it. I submitted a bug report and a workaround > patch for ctfmerge to the Illumos guys but they have been very slow > to review it as well. >=20 > I do agree having out-of-tree compilers is important though; and > much preferable than carrying two compilers ;). Is this patch in the ports version of gcc at least? Warner