From owner-freebsd-arch@FreeBSD.ORG Sun Jan 13 19:33:13 2013 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 867FE972 for ; Sun, 13 Jan 2013 19:33:13 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) by mx1.freebsd.org (Postfix) with ESMTP id 57BA17AE for ; Sun, 13 Jan 2013 19:33:13 +0000 (UTC) Received: by mail-ie0-f180.google.com with SMTP id c10so4306813ieb.11 for ; Sun, 13 Jan 2013 11:33:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received: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=diRGXwPkVjGVTdMS1l+l8Qg4+PYb0FKHdeo2V+PwSrQ=; b=Vkg0gJinWqD7vYglc/xKjHYgW5SoxV8Foc0pMk3pgYDl/9NlJKl5MXmsdlHLFRNj/7 so9paOnv5lAFYSH1tk/UTjrRdnvT06HSOvEtZVHwfvo7lb0+4xAJ5luXnuzyyZwJgqL5 wPR4TRyGsGcOJan23pUdUm+cOFpZN00R3fYXdVgWg+/RpqiHV3CtIl8g0sNSp9VCzy1E b4DtVVIdK25Y6Mlel6jrQy6QSWn6aapNgfV+URSvkDORLf3hbfvEXj/E0ObhCWnglq9S p+czATKxcsKmP9CZR6IrZmondBOlpkP+N+l/4blFX6jhwiPUuhd+GEcU29QMpaT/L2wc MBDw== X-Received: by 10.42.94.8 with SMTP id z8mr62130733icm.36.1358105592576; Sun, 13 Jan 2013 11:33:12 -0800 (PST) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id bg10sm4696420igc.6.2013.01.13.11.33.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Jan 2013 11:33:11 -0800 (PST) Sender: Warner Losh Subject: Re: how long to keep support for gcc on x86? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20130113053725.GL1410@funkthat.com> Date: Sun, 13 Jan 2013 12:33:09 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130112233147.GK1410@funkthat.com> <20130113014242.GA61609@troutmask.apl.washington.edu> <20130113053725.GL1410@funkthat.com> To: John-Mark Gurney X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQnyXt8mg4Kg69s9A+pasMlKmERnEenJ+jtSsLlzbza+eE0UQdTityfgdliGXt5BIhw03Dpd Cc: Adrian Chadd , Steve Kargl , freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 19:33:13 -0000 On Jan 12, 2013, at 10:37 PM, John-Mark Gurney wrote: > Adrian Chadd wrote this message on Sat, Jan 12, 2013 at 19:30 -0800: >> IMHO gcc shuld be available until all of the platforms that we >> currently ship FreeBSD on gets clang support. >=20 > Though, we have a very ancient version of gcc, a modern version would > support the AES-NI intrinsicts that I am thinking of using... It's > more of a question of how long do we need to keep support for gcc > 4.2.1, not another modern gcc/other compiler... You have to support what's in the tree. In the past when people have wanted to use newer instructions, which is = more a binutils thing anyway, they have added support to them in our = in-tree binutils. >> This includes MIPS (which is there, but I don't think the default = MIPS >> build uses clang at the moment) and ia64, which Marcel has been >> dutifully working on. >>=20 >> Please also note that people can and will compile FreeBSD on a >> non-default-system compiler ; so deprecating gcc (either support or >> framework) should be considered carefully. >=20 > Considering that the icc stuff was recently removed, unless the = compiler > has good gcc/clang emulation, I can't see how far another compiler = would > get compiling our code... clang support isn't even complete yet. There are still numerous = unresolved warnings on i386 and amd64 that gcc doesn't complain about. = It is far too premature for desupporting gcc compiles of the kernel. Warner >> On 12 January 2013 17:42, Steve Kargl = wrote: >>> On Sat, Jan 12, 2013 at 03:31:47PM -0800, John-Mark Gurney wrote: >>>> So, now that -current x86 is defaulting to clang, how much longer = do we >>>> need to support gcc on platforms that default to clang? >>>=20 >>> IMHO, gcc should be available until after 10.0 is branched. >>>=20 >>>> I'm asking because clang support AES-NI, but gcc does not... >>>=20 >>> The last and only time I had for testing clang's handling >>> of floating point revealed that clang had a few bugs and >>> performance issues. >=20 > --=20 > John-Mark Gurney Voice: +1 415 225 5579 >=20 > "All that I will do, has been done, All that I have, has not." > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to = "freebsd-arch-unsubscribe@freebsd.org"