From owner-freebsd-toolchain@FreeBSD.ORG Thu Aug 22 20:09:06 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9A9513BC; Thu, 22 Aug 2013 20:09:06 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 786472B43; Thu, 22 Aug 2013 20:09:03 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r7MK92er091302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Aug 2013 13:09:02 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r7MK92PS091301; Thu, 22 Aug 2013 13:09:02 -0700 (PDT) (envelope-from jmg) Date: Thu, 22 Aug 2013 13:09:02 -0700 From: John-Mark Gurney To: toolchain@FreeBSD.org, current@FreeBSD.org Subject: patch to add AES intrinsics to gcc Message-ID: <20130822200902.GG94127@funkthat.com> Mail-Followup-To: toolchain@FreeBSD.org, current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Thu, 22 Aug 2013 13:09:02 -0700 (PDT) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Aug 2013 20:09:06 -0000 In my work to get AES-NI performance in a better state and the fact that we haven't deprecated gcc yet, I have developed another patch to add the appropriate AES intrinstic headers to gcc. The patch is available at: https://people.freebsd.org/~jmg/gcc.aes.intrin.patch I did have to change the opth-gen.awk script, since it wouldn't let me use bit 31, and recent changes to gcc used up all the remaining bits. I also was unable to add the -mpclmul option because of running out of these bits. Thanks. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 09:17:07 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 67359659; Fri, 23 Aug 2013 09:17:07 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1A3F32867; Fri, 23 Aug 2013 09:17:06 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7N9H2gs051621 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 23 Aug 2013 09:17:04 GMT (envelope-from theraven@FreeBSD.org) Content-Type: multipart/signed; boundary="Apple-Mail=_407EAE74-9C84-4000-8909-A8E10545B6F3"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: patch to add AES intrinsics to gcc From: David Chisnall In-Reply-To: <20130822200902.GG94127@funkthat.com> Date: Fri, 23 Aug 2013 10:16:56 +0100 Message-Id: <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> References: <20130822200902.GG94127@funkthat.com> To: John-Mark Gurney X-Mailer: Apple Mail (2.1508) Cc: toolchain@FreeBSD.org, current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 09:17:07 -0000 --Apple-Mail=_407EAE74-9C84-4000-8909-A8E10545B6F3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I have a patch that I intend to commit before the 10.0 code slush that = removes GCC and libstdc++ from the default build on platforms where = clang is the system compiler. We definitely don't want to be supporting = our 6-year-old versions of these for the lifetime of the 10.x branch. =20= David On 22 Aug 2013, at 21:09, John-Mark Gurney wrote: > In my work to get AES-NI performance in a better state and the fact > that we haven't deprecated gcc yet, I have developed another patch to > add the appropriate AES intrinstic headers to gcc. >=20 > The patch is available at: > https://people.freebsd.org/~jmg/gcc.aes.intrin.patch >=20 > I did have to change the opth-gen.awk script, since it wouldn't let > me use bit 31, and recent changes to gcc used up all the remaining > bits. I also was unable to add the -mpclmul option because of running > out of these bits. >=20 > Thanks. >=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-toolchain@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain > To unsubscribe, send any mail to = "freebsd-toolchain-unsubscribe@freebsd.org" --Apple-Mail=_407EAE74-9C84-4000-8909-A8E10545B6F3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJSFyiIAAoJEKx65DEEsqIdBDQP/0F0wPcrxwyybC45ON0WVUa5 3qGsXSQppYVl5NGXZI9UBROd1fIeQQjiCLFMwEBPVLWgnxC+91HIjTUXVR9zsd4z E2ze0BwPI26i+4tfvcFraLhbv4F7rjlp5hHwzHlPLyc5CgNv7w4U7jCCOBZ565J3 pTBz3IXgo7rFkXrfXFmGoX2yPD1v8xtoh22saAltfy6MgViROZbDD3nZhMqU7Mh4 HUOKdIwoBbmrnqC1o+5Pwza6v/4xs1z8wVXJoBl5ayI9BYk+UUXVCcnQQH1OIHUa lyVN5n3SWvuNnWGw+dLoQ85bydk5ZXyM4H/d+/rd8y7MioIdtJ4TC4+6JJJ9y8hH eDP9kekGu7triDJvRbvvZuurlwe90MUso0mswqUqsGLvR5aKAWQTTgqqMBJACW+n YdKuJn8gdIKRBhs2S5/KpyjhVFJxZfBOjvxjjg1iX2T12uYxEt0+Ssz6UI5Yok2Z SiwPvX+S1fDpJH6D9Dd8vh+Nj2TC2ntnKGyTliMpmv+NyWyF5DhqZqR1QN0kEhi2 yoLD+9ZJRMemKAdqcY9PDKnk+5qV6EOeswOP0k9xZnHx/wx8ibvIDkOhpVGR8hw8 UuYAyjGhTKFX0Al8pzZr1Bxgg50lO8ojvbUI+C22Qf6BrVFUaqF1FWuyhOWwI/jm NyJAW0itc3PmuW4mycMr =Hcyv -----END PGP SIGNATURE----- --Apple-Mail=_407EAE74-9C84-4000-8909-A8E10545B6F3-- From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 09:39:10 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6188AE59; Fri, 23 Aug 2013 09:39:10 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4C44C2978; Fri, 23 Aug 2013 09:39:08 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA27006; Fri, 23 Aug 2013 12:39:07 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1VCnpj-000PKi-6K; Fri, 23 Aug 2013 12:39:07 +0300 Message-ID: <52172D96.8090801@FreeBSD.org> Date: Fri, 23 Aug 2013 12:38:30 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130810 Thunderbird/17.0.8 MIME-Version: 1.0 To: David Chisnall Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0__43183.8718745441$1377249444$gmane$org@FreeBSD.org> In-Reply-To: <105E26EE-8471-49D3-AB57-FBE2779CF8D0__43183.8718745441$1377249444$gmane$org@FreeBSD.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: toolchain@FreeBSD.org, current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 09:39:10 -0000 on 23/08/2013 12:16 David Chisnall said the following: > I have a patch that I intend to commit before the 10.0 code slush that > removes GCC and libstdc++ from the default build on platforms where clang > is the system compiler. We definitely don't want to be supporting our > 6-year-old versions of these for the lifetime of the 10.x branch. I have an alternative proposal (to re@ and core@) to set WITHOUT_CLANG_IS_CC in stable/10 or at least releng/10.0. -- Andriy Gapon From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 09:58:58 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 90BC2670 for ; Fri, 23 Aug 2013 09:58:58 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 54F562AAD for ; Fri, 23 Aug 2013 09:58:55 +0000 (UTC) Received: by mail-ob0-f175.google.com with SMTP id xn12so462933obc.20 for ; Fri, 23 Aug 2013 02:58:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=XEgJvnNR1IUQmRZhgrqYaA0FXiEyMvuqwnQGIDFw/q8=; b=f/CO8BWVUDy/7jH+vXg60uldMJwbvJqLGChFiPRW3mqHGe4BND8ZrcNleuOV0cN54T tUVUviF5fQXI91R0oZD1u40/FE/qT2GycTl5Ut6wylq4PcI7MnxtZGhpB8qKihBRa2fe 1QUHDovWEBC6f6z6gXQDpWsFIVOi7PnpVQiC4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=XEgJvnNR1IUQmRZhgrqYaA0FXiEyMvuqwnQGIDFw/q8=; b=EYeTw/eGL1EsCKOChR9FSUraMySy5uIV/6xvkQWTrDK5+k/5fJ/J6BmrMynqeqbqjN 29yt27qwgEpdUd8bZO00wjaZuX+Q41ST4ZF2p/sWANevFzgg23BD8KC58PWgMXSbKPwB EVz6P18KZSTcu0L46/6a3UgXuyiGeofzNk3LXzeHOa7yjjvAKN3G3whyHgzY3yucrQDO lSqKeZrQIamerMDrBlVWTXCQrLMzHF+3Pkg2HvbvXLDYnp9dIkFD7WwM8Qzbf2nr21dZ o6y24BprvLtr6l5Oa+VRubu1cjVLwTkn5O7R/u9YFuyTP10mKQhPUANEdS56J5mmduaE H9cw== X-Gm-Message-State: ALoCoQnx+nOZlGdznTXFXgFHz+NbYcYhZ0SsFBXsalxpN7UY2DTcLbXwUzXNmLSND3tzEoCgBAD2 MIME-Version: 1.0 X-Received: by 10.182.129.233 with SMTP id nz9mr19479518obb.8.1377251934542; Fri, 23 Aug 2013 02:58:54 -0700 (PDT) Sender: decke@bluelife.at Received: by 10.76.81.4 with HTTP; Fri, 23 Aug 2013 02:58:54 -0700 (PDT) X-Originating-IP: [80.123.233.199] In-Reply-To: <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> Date: Fri, 23 Aug 2013 11:58:54 +0200 X-Google-Sender-Auth: jmT25XPIOmeQOuW9TJDRO5p_DIg Message-ID: Subject: Re: patch to add AES intrinsics to gcc From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= To: David Chisnall Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: toolchain@freebsd.org, John-Mark Gurney , current@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 09:58:58 -0000 I don't know if you are aware that IF you really do that we will have serio= us problems to ship packages for 10. USE_GCC=3Dany is the fallback in the portstree for all ports that are unable to build with clang which was intro= duced when HEAD switched to clang as default cc. Right now there are 150 ports in the tree that use this fallback and quite a few of them are high profile po= rts: the highlights: audio/nas devel/mingw32-binutils emulators/qemu emulators/virtualbox-ose emulators/wine lang/go lang/v8 mail/courier math/fftw3 multimedia/libxine multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 security/clamav the full list: http://dpaste.com/1354075/ A possible hack could be to add a check for USE_GCC=3Dany to behave like a USE_GCC=3Dyes on HEAD on the affected platforms. This pulls in lang/gcc from ports for a lot of people on HEAD I suppose. We certainly need to do that switch to remove the ancient gcc from base some time but with my portmgr hat on I can only say we don't plan to do tha= t before 10.0 especially not if we are only talking about a few weeks time wi= ndow. --=20 Bernhard Froehlich http://www.bluelife.at/ On Fri, Aug 23, 2013 at 11:16 AM, David Chisnall wro= te: > I have a patch that I intend to commit before the 10.0 code slush that re= moves GCC and libstdc++ from the default build on platforms where clang is = the system compiler. We definitely don't want to be supporting our 6-year-= old versions of these for the lifetime of the 10.x branch. > > David > > On 22 Aug 2013, at 21:09, John-Mark Gurney wrote: > >> In my work to get AES-NI performance in a better state and the fact >> that we haven't deprecated gcc yet, I have developed another patch to >> add the appropriate AES intrinstic headers to gcc. >> >> The patch is available at: >> https://people.freebsd.org/~jmg/gcc.aes.intrin.patch >> >> I did have to change the opth-gen.awk script, since it wouldn't let >> me use bit 31, and recent changes to gcc used up all the remaining >> bits. I also was unable to add the -mpclmul option because of running >> out of these bits. >> >> Thanks. >> >> -- >> John-Mark Gurney Voice: +1 415 225 5579 >> >> "All that I will do, has been done, All that I have, has not." >> _______________________________________________ >> freebsd-toolchain@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain >> To unsubscribe, send any mail to "freebsd-toolchain-unsubscribe@freebsd.= org" From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 10:35:49 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CD8DBCCF; Fri, 23 Aug 2013 10:35:49 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 983DA2C89; Fri, 23 Aug 2013 10:35:49 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7NAZjLl052159 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 23 Aug 2013 10:35:46 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: patch to add AES intrinsics to gcc From: David Chisnall In-Reply-To: Date: Fri, 23 Aug 2013 11:35:40 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> To: =?iso-8859-1?Q?Bernhard_Fr=F6hlich?= X-Mailer: Apple Mail (2.1508) Cc: toolchain@FreeBSD.org, John-Mark Gurney , "re@FreeBSD.org Engineering Team" , current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 10:35:49 -0000 On 23 Aug 2013, at 10:58, Bernhard Fr=F6hlich wrote: > I don't know if you are aware that IF you really do that we will have = serious > problems to ship packages for 10. USE_GCC=3Dany is the fallback in the > portstree for all ports that are unable to build with clang which was = introduced > when HEAD switched to clang as default cc. Right now there are 150 = ports in > the tree that use this fallback and quite a few of them are high = profile ports: >=20 > the highlights: > audio/nas devel/mingw32-binutils emulators/qemu = emulators/virtualbox-ose > emulators/wine lang/go lang/v8 mail/courier math/fftw3 = multimedia/libxine > multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 > security/clamav >=20 > the full list: > http://dpaste.com/1354075/ >=20 > A possible hack could be to add a check for USE_GCC=3Dany to behave = like > a USE_GCC=3Dyes on HEAD on the affected platforms. This pulls in = lang/gcc > from ports for a lot of people on HEAD I suppose. >=20 > We certainly need to do that switch to remove the ancient gcc from = base > some time but with my portmgr hat on I can only say we don't plan to = do that > before 10.0 especially not if we are only talking about a few weeks = time window. That is unfortunate. We have said for over a year that 10.0 should not = ship with gcc. I can delay committing the patch to flip the switch = until later in the code slush, if re approves, but ports that require = gcc should be building with gcc from ports (which will also improve code = quality, as gcc 4.6/7 produce significantly better code than 4.2.1). David From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 10:42:33 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1F11AE90; Fri, 23 Aug 2013 10:42:33 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C63722CE9; Fri, 23 Aug 2013 10:42:32 +0000 (UTC) Received: from jre-mbp.elischer.org (etroy.elischer.org [121.45.226.51]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.6) with ESMTP id r7NAgQVT015537 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 23 Aug 2013 03:42:29 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52173C8D.20608@freebsd.org> Date: Fri, 23 Aug 2013 18:42:21 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: David Chisnall Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> In-Reply-To: <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: toolchain@FreeBSD.org, John-Mark Gurney , current@FreeBSD.org, "re@FreeBSD.org Engineering Team" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 10:42:33 -0000 On 8/23/13 6:35 PM, David Chisnall wrote: > On 23 Aug 2013, at 10:58, Bernhard Fröhlich wrote: > >> I don't know if you are aware that IF you really do that we will have serious >> problems to ship packages for 10. USE_GCC=any is the fallback in the >> portstree for all ports that are unable to build with clang which was introduced >> when HEAD switched to clang as default cc. Right now there are 150 ports in >> the tree that use this fallback and quite a few of them are high profile ports: >> >> the highlights: >> audio/nas devel/mingw32-binutils emulators/qemu emulators/virtualbox-ose >> emulators/wine lang/go lang/v8 mail/courier math/fftw3 multimedia/libxine >> multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 >> security/clamav >> >> the full list: >> http://dpaste.com/1354075/ >> >> A possible hack could be to add a check for USE_GCC=any to behave like >> a USE_GCC=yes on HEAD on the affected platforms. This pulls in lang/gcc >> from ports for a lot of people on HEAD I suppose. >> >> We certainly need to do that switch to remove the ancient gcc from base >> some time but with my portmgr hat on I can only say we don't plan to do that >> before 10.0 especially not if we are only talking about a few weeks time window. > That is unfortunate. We have said for over a year that 10.0 should not ship with gcc. I can delay committing the patch to flip the switch until later in the code slush, if re approves, but ports that require gcc should be building with gcc from ports (which will also improve code quality, as gcc 4.6/7 produce significantly better code than 4.2.1). no, I believe we have said that 10 would ship with clang by default. NO mention was made about gcc being absent, and I am uncomfortable with taking that step yet. Having gcc just present, will not hurt you.. even after it is gone we will need to support those who will be replacing clang with newer versions of gcc in hteir own products. > > David > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 11:02:20 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E9B41429; Fri, 23 Aug 2013 11:02:20 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward4l.mail.yandex.net (forward4l.mail.yandex.net [IPv6:2a02:6b8:0:1819::4]) by mx1.freebsd.org (Postfix) with ESMTP id ABA2A2DF5; Fri, 23 Aug 2013 11:02:20 +0000 (UTC) Received: from smtp14.mail.yandex.net (smtp14.mail.yandex.net [95.108.131.192]) by forward4l.mail.yandex.net (Yandex) with ESMTP id 377C9144105D; Fri, 23 Aug 2013 15:02:19 +0400 (MSK) Received: from smtp14.mail.yandex.net (localhost [127.0.0.1]) by smtp14.mail.yandex.net (Yandex) with ESMTP id B6C101B608C4; Fri, 23 Aug 2013 15:02:18 +0400 (MSK) Received: from 93.91.10.81.tel.ru (93.91.10.81.tel.ru [93.91.10.81]) by smtp14.mail.yandex.net (nwsmtp/Yandex) with ESMTP id RaB1TxKpTq-2IauTQRu; Fri, 23 Aug 2013 15:02:18 +0400 Message-ID: <5217413A.9080105@passap.ru> Date: Fri, 23 Aug 2013 15:02:18 +0400 From: Boris Samorodov Organization: =?UTF-8?B?0JfQkNCeICLQktCQ0KDQoiI=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130806 Thunderbird/17.0.7 MIME-Version: 1.0 To: David Chisnall Subject: GCC withdraw (was: Re: patch to add AES intrinsics to gcc) References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> In-Reply-To: <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: toolchain@FreeBSD.org, John-Mark Gurney , current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 11:02:21 -0000 23.08.2013 13:16, David Chisnall пишет: > I have a patch that I intend to commit before the 10.0 code slush that removes GCC and libstdc++ from the default build on platforms where clang is the system compiler. We definitely don't want to be supporting our 6-year-old versions of these for the lifetime of the 10.x branch. Isn't it a POLA violation? As for me I expect something like this: . 9.x gcc default and clang in base; . 10.x clang default and gcc in base; . 11.x gcc withdraw. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 11:06:15 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4F1C759A; Fri, 23 Aug 2013 11:06:15 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0E7132E20; Fri, 23 Aug 2013 11:06:14 +0000 (UTC) Received: from c120.sec.cl.cam.ac.uk (c120.sec.cl.cam.ac.uk [128.232.18.120]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7NB6Cmd052435 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 23 Aug 2013 11:06:13 GMT (envelope-from theraven@FreeBSD.org) Content-Type: multipart/signed; boundary="Apple-Mail=_25C04FD8-9B62-4151-9440-9259D8707223"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: patch to add AES intrinsics to gcc From: David Chisnall In-Reply-To: <52173C8D.20608@freebsd.org> Date: Fri, 23 Aug 2013 12:06:10 +0100 Message-Id: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> To: Julian Elischer X-Mailer: Apple Mail (2.1508) Cc: toolchain@FreeBSD.org, John-Mark Gurney , current@FreeBSD.org, "re@FreeBSD.org Engineering Team" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 11:06:15 -0000 --Apple-Mail=_25C04FD8-9B62-4151-9440-9259D8707223 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 23 Aug 2013, at 11:42, Julian Elischer wrote: > no, I believe we have said that 10 would ship with clang by default. = NO mention was made about gcc being absent, and I am uncomfortable with = taking that step yet. Having gcc just present, will not hurt you.. even = after it is gone we will need to support those who will be replacing = clang with newer versions of gcc in hteir own products. The plan is not to delete gcc from the tree, it is to disable building = gcc by default when clang is the system compiler. If you are building = products then you are perfectly at liberty to set WITH_GCC=3Dyes in your = src.conf. Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in = its atomic generation so you can't use it sensibly without lots of = inline assembly (which it doesn't support for newer architectures) for = multithreaded things. Our libstdc++ is ancient and doesn't work with modern C++ codebases. = Putting them in the base system means that people will use them. If = anyone wants them to remain, then speak now and this will be taken as = your volunteering to: - Maintain our forks of both gcc and libstdc++ - Handle every single PR that is filed by people using these If you are willing to do this, then that's great. If not, then you are = asking other people to support ancient codebases that they are not = using. David --Apple-Mail=_25C04FD8-9B62-4151-9440-9259D8707223 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJSF0IiAAoJEKx65DEEsqId+k4P/RFwL2MtORKKi4copj9dKJ3r f/Uh7vfFAqFmk3w/itKSCVictHJngqSXhopXpo7PIRob7hh+pVkF1fUd7a69bJH5 XaTslr3zJeQGZBsZGdYGKHeDaX33Y2r7VSaqUrk8EJfJwNffzQbBWkUA0YIYC/Xh cmYh/3CIDclemBPgRH1GQR78n9yuf3yZK/r22HMr2aPS/YWGfn0MQiEbEL0OgsMP 7uOYmXpmXiTcrJQEaBb4chS0PT4vPC4PJKbaRDCyhzSy1CuIWJjjDPyWco4WB/RY ssBQo/g/AFlANYdkuLk+9T860oS93/eotnbPifux5zvjKCFpk3JZwclBJI35sclk syqLfZHwskvmWa8cA6IuGQNBgpbBmOfVK65HwTPQ9+B14aQ83euKI2PQywtFW/dp maMYs65dRfhDdazzytTzPqemRc9CZfqt0sV9qfpqAReDTiKTV2hfcY/UCkoy9+7F 2gICFQAWFPuod47TUyWb8v94zfCmgnZvhdtZkomZ3wxntYTt5A6cioDO8yIbhqrh wF65WCvffKMQa/J4JdvsaFAm07F0KLxJ/fdEaskqoh5UnfU3sFRiK2oAHloSBblt uK+b/847HM1NEH/f5pBiiIj2cT+ANl2cWR15n5YJEwUg02b/c+30iq5DFv5X3yYx Xh33KOvh35quLXx//8yg =ZDGR -----END PGP SIGNATURE----- --Apple-Mail=_25C04FD8-9B62-4151-9440-9259D8707223-- From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 11:16:51 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B4294956; Fri, 23 Aug 2013 11:16:51 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 715C62EDA; Fri, 23 Aug 2013 11:16:51 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1VCpMF-000ECZ-Qc; Fri, 23 Aug 2013 13:16:47 +0200 Date: Fri, 23 Aug 2013 13:16:47 +0200 From: Kurt Jaeger To: current@FreeBSD.org Subject: Re: GCC withdraw (was: Re: patch to add AES intrinsics to gcc) Message-ID: <20130823111647.GT2951@home.opsec.eu> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5217413A.9080105@passap.ru> Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 11:16:51 -0000 Hi! > > I have a patch that I intend to commit before the 10.0 code > > slush that removes GCC and libstdc++ from the default build on > > platforms where clang is the system compiler. We definitely don't > > want to be supporting our 6-year-old versions of these for the > > lifetime of the 10.x branch. > > Isn't it a POLA violation? > > As for me I expect something like this: > . 9.x gcc default and clang in base; > . 10.x clang default and gcc in base; > . 11.x gcc withdraw. If the 150 ports that only work with gcc, all work with a ports gcc and do not need the gcc from base, would the following be OK ? - 9.x gcc default and clang in base; - 10.x clang default and gcc in ports; -- pi@opsec.eu +49 171 3101372 7 years to go ! From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 11:21:56 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B5853B12 for ; Fri, 23 Aug 2013 11:21:56 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 78F1B2F26 for ; Fri, 23 Aug 2013 11:21:56 +0000 (UTC) Received: by mail-ob0-f169.google.com with SMTP id wc20so548032obb.0 for ; Fri, 23 Aug 2013 04:21:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=S1ff7/DtEv5fO5qrDfQjqbn3G4f0VR8bkrUbfhfUWR4=; b=H6Clcek0tOOOSo+K9T9wdHmvg4vSutrNgNF0wzQNCxWxDreUl/ZLcogclrjWaZ/nCT EO1WEp4BnRQsn/gH5Nii/22+HwGIb2/vjKfN+bje9GvKkpim8QGVeJY58XLXpEpmiVME Fg0VIWZ5eVe26YOWau3r+k8QQo3SbqKZI4PL4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=S1ff7/DtEv5fO5qrDfQjqbn3G4f0VR8bkrUbfhfUWR4=; b=U7nqu/UF3ngeCAZQuGNz9lsArHfE1PH3pXSbMz4jtokbboSxFoniNpUnU6Cwp4pF4P Mi8nSvtdYmaspRGfN15wUkrVWiBlt8AyiG3pEMs2DXKOVCaH4qhnDrGZvJFrbEU+T/D9 7ZIfRHJ2Ke20Zd/7B7KX8l1dcqqmDcYiiCus3DVYPeQ8UoO4lmeqPSebZzLmUqs0a7er +3B3QGSGMG0nNGzHpi+o32Svri46lHVa6fFovq6sVahDQKyJHLXgq6/1bkQqvsFtLI5Z fDAmtdURC2mjAk4pqmncpy6edf9HrU77mgwPFWKOpEB3N+ak3Tj/Nf7309RQfvKlZiIK YGZA== X-Gm-Message-State: ALoCoQlFkQI4LiX8nUQCRHIgFoNMwmJrl2hHuRv5UoCl7gz4pmie61YuhKfHN+EWKpoAfa0lARci MIME-Version: 1.0 X-Received: by 10.60.62.101 with SMTP id x5mr19638756oer.24.1377256915806; Fri, 23 Aug 2013 04:21:55 -0700 (PDT) Sender: decke@bluelife.at Received: by 10.76.81.4 with HTTP; Fri, 23 Aug 2013 04:21:55 -0700 (PDT) X-Originating-IP: [80.123.233.199] In-Reply-To: <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> Date: Fri, 23 Aug 2013 13:21:55 +0200 X-Google-Sender-Auth: 6SmX1HAo4Echz8lO4wP7i5EH7Wo Message-ID: Subject: Re: patch to add AES intrinsics to gcc From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= To: David Chisnall Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: toolchain@freebsd.org, John-Mark Gurney , "re@FreeBSD.org Engineering Team" , current@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 11:21:56 -0000 On Fri, Aug 23, 2013 at 12:35 PM, David Chisnall wro= te: > On 23 Aug 2013, at 10:58, Bernhard Fr=F6hlich wrote: > >> I don't know if you are aware that IF you really do that we will have se= rious >> problems to ship packages for 10. USE_GCC=3Dany is the fallback in the >> portstree for all ports that are unable to build with clang which was in= troduced >> when HEAD switched to clang as default cc. Right now there are 150 ports= in >> the tree that use this fallback and quite a few of them are high profile= ports: >> >> the highlights: >> audio/nas devel/mingw32-binutils emulators/qemu emulators/virtualbox-ose >> emulators/wine lang/go lang/v8 mail/courier math/fftw3 multimedia/libxin= e >> multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 >> security/clamav >> >> the full list: >> http://dpaste.com/1354075/ >> >> A possible hack could be to add a check for USE_GCC=3Dany to behave like >> a USE_GCC=3Dyes on HEAD on the affected platforms. This pulls in lang/gc= c >> from ports for a lot of people on HEAD I suppose. >> >> We certainly need to do that switch to remove the ancient gcc from base >> some time but with my portmgr hat on I can only say we don't plan to do = that >> before 10.0 especially not if we are only talking about a few weeks time= window. > > That is unfortunate. We have said for over a year that 10.0 should not s= hip with gcc. I can delay committing the patch to flip the switch until la= ter in the code slush, if re approves, but ports that require gcc should be= building with gcc from ports (which will also improve code quality, as gcc= 4.6/7 produce significantly better code than 4.2.1). I have asked the question of "when will gcc be removed from base" multiple times over the last year and I got varying results back with the majority s= aying "after 10". I'm just trying to say that It looks like some people in src also don't expect it to be removed in 10. Anyway bapt already did some testing without gcc in base on HEAD and the results were bad but not totally awful. We will see if we can fix the most important ones in time before 10 but we can't promise anything. If someone wants to have a look at the failures with no gcc in base on HEAD= : http://pb2.nyi.freebsd.org/bulk/nogcc-default/2013-08-04_01h01m20s/ (this also includes HEAD failures caused by clang) --=20 Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 11:22:28 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D8EDFC4E; Fri, 23 Aug 2013 11:22:28 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward8l.mail.yandex.net (forward8l.mail.yandex.net [IPv6:2a02:6b8:0:1819::8]) by mx1.freebsd.org (Postfix) with ESMTP id 9CC692F3C; Fri, 23 Aug 2013 11:22:28 +0000 (UTC) Received: from smtp3h.mail.yandex.net (smtp3h.mail.yandex.net [84.201.186.20]) by forward8l.mail.yandex.net (Yandex) with ESMTP id 6911F1A40D8B; Fri, 23 Aug 2013 15:22:27 +0400 (MSK) Received: from smtp3h.mail.yandex.net (localhost [127.0.0.1]) by smtp3h.mail.yandex.net (Yandex) with ESMTP id 0F6751B41643; Fri, 23 Aug 2013 15:22:26 +0400 (MSK) Received: from 93.91.10.81.tel.ru (93.91.10.81.tel.ru [93.91.10.81]) by smtp3h.mail.yandex.net (nwsmtp/Yandex) with ESMTP id pXTbhHIe95-MQtGVhhe; Fri, 23 Aug 2013 15:22:26 +0400 To: undisclosed-recipients:; Message-ID: <521745F2.8050607@passap.ru> Date: Fri, 23 Aug 2013 15:22:26 +0400 From: Boris Samorodov Organization: =?UTF-8?B?0JfQkNCeICLQktCQ0KDQoiI=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130806 Thunderbird/17.0.7 MIME-Version: 1.0 Subject: Re: GCC withdraw References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> In-Reply-To: <20130823111647.GT2951@home.opsec.eu> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: toolchain@FreeBSD.org, current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 11:22:28 -0000 23.08.2013 15:16, Kurt Jaeger пишет: > Hi! > >>> I have a patch that I intend to commit before the 10.0 code >>> slush that removes GCC and libstdc++ from the default build on >>> platforms where clang is the system compiler. We definitely don't >>> want to be supporting our 6-year-old versions of these for the >>> lifetime of the 10.x branch. >> >> Isn't it a POLA violation? >> >> As for me I expect something like this: >> . 9.x gcc default and clang in base; >> . 10.x clang default and gcc in base; >> . 11.x gcc withdraw. > > If the 150 ports that only work with gcc, all work with a ports > gcc and do not need the gcc from base, would the following be OK ? > > - 9.x gcc default and clang in base; > - 10.x clang default and gcc in ports; Well, we write rules and we brake them. ;-) Just say that we know we brake them but it's inevitable because... And go futher. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 11:44:29 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 89318357; Fri, 23 Aug 2013 11:44:29 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 44E2E20C9; Fri, 23 Aug 2013 11:44:29 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VCpp5-000H4z-AK; Fri, 23 Aug 2013 15:46:35 +0400 Date: Fri, 23 Aug 2013 15:46:35 +0400 From: Slawa Olhovchenkov To: Julian Elischer Subject: Re: patch to add AES intrinsics to gcc Message-ID: <20130823114635.GB64913@zxy.spb.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52173C8D.20608@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: "re@FreeBSD.org Engineering Team" , current@FreeBSD.org, John-Mark Gurney , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 11:44:29 -0000 On Fri, Aug 23, 2013 at 06:42:21PM +0800, Julian Elischer wrote: > On 8/23/13 6:35 PM, David Chisnall wrote: > > On 23 Aug 2013, at 10:58, Bernhard Fr?hlich wrote: > > > >> I don't know if you are aware that IF you really do that we will have serious > >> problems to ship packages for 10. USE_GCC=any is the fallback in the > >> portstree for all ports that are unable to build with clang which was introduced > >> when HEAD switched to clang as default cc. Right now there are 150 ports in > >> the tree that use this fallback and quite a few of them are high profile ports: > >> > >> the highlights: > >> audio/nas devel/mingw32-binutils emulators/qemu emulators/virtualbox-ose > >> emulators/wine lang/go lang/v8 mail/courier math/fftw3 multimedia/libxine > >> multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 > >> security/clamav > >> > >> the full list: > >> http://dpaste.com/1354075/ > >> > >> A possible hack could be to add a check for USE_GCC=any to behave like > >> a USE_GCC=yes on HEAD on the affected platforms. This pulls in lang/gcc > >> from ports for a lot of people on HEAD I suppose. > >> > >> We certainly need to do that switch to remove the ancient gcc from base > >> some time but with my portmgr hat on I can only say we don't plan to do that > >> before 10.0 especially not if we are only talking about a few weeks time window. > > That is unfortunate. We have said for over a year that 10.0 should not ship with gcc. I can delay committing the patch to flip the switch until later in the code slush, if re approves, but ports that require gcc should be building with gcc from ports (which will also improve code quality, as gcc 4.6/7 produce significantly better code than 4.2.1). > no, I believe we have said that 10 would ship with clang by default. 10 from this winner have broken firewire code when building by clang -- cannot resume from sleep. From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 11:54:20 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5F1DF5CE; Fri, 23 Aug 2013 11:54:20 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.21.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DE70D214B; Fri, 23 Aug 2013 11:54:19 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [193.68.6.1]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.6/8.14.6) with ESMTP id r7NBrr9I011536 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 23 Aug 2013 14:53:54 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <52174D51.2050601@digsys.bg> Date: Fri, 23 Aug 2013 14:53:53 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130812 Thunderbird/17.0.8 MIME-Version: 1.0 To: Kurt Jaeger Subject: Re: GCC withdraw References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> In-Reply-To: <20130823111647.GT2951@home.opsec.eu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: toolchain@FreeBSD.org, current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 11:54:20 -0000 On 23.08.13 14:16, Kurt Jaeger wrote: > Hi! > >>> I have a patch that I intend to commit before the 10.0 code >>> slush that removes GCC and libstdc++ from the default build on >>> platforms where clang is the system compiler. We definitely don't >>> want to be supporting our 6-year-old versions of these for the >>> lifetime of the 10.x branch. >> Isn't it a POLA violation? >> >> As for me I expect something like this: >> . 9.x gcc default and clang in base; >> . 10.x clang default and gcc in base; >> . 11.x gcc withdraw. > If the 150 ports that only work with gcc, all work with a ports > gcc and do not need the gcc from base, would the following be OK ? > > - 9.x gcc default and clang in base; > - 10.x clang default and gcc in ports; > I believe this is the best idea so far. As long as these ports work with gcc in ports, that is. For many of the "important" ports, they do get used together with other ports that already require newer gcc from ports anyway. So no additional pollution will be created. Daniel From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 11:55:48 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1346C705; Fri, 23 Aug 2013 11:55:48 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id CC34E215E; Fri, 23 Aug 2013 11:55:47 +0000 (UTC) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 1F5323AE30; Fri, 23 Aug 2013 11:55:41 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.7/8.14.7) with ESMTP id r7NBtexF021415; Fri, 23 Aug 2013 11:55:40 GMT (envelope-from phk@phk.freebsd.dk) To: Daniel Kalchev Subject: Re: GCC withdraw In-reply-to: <52174D51.2050601@digsys.bg> From: "Poul-Henning Kamp" References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <52174D51.2050601@digsys.bg> Content-Type: text/plain; charset=ISO-8859-1 Date: Fri, 23 Aug 2013 11:55:40 +0000 Message-ID: <21414.1377258940@critter.freebsd.dk> Cc: toolchain@FreeBSD.org, Kurt Jaeger , current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 11:55:48 -0000 In message <52174D51.2050601@digsys.bg>, Daniel Kalchev writes: >> - 9.x gcc default and clang in base; >> - 10.x clang default and gcc in ports; > >I believe this is the best idea so far. As long as these ports work with >gcc in ports, that is. +1 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 12:12:37 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C2579D28; Fri, 23 Aug 2013 12:12:37 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AB28B2290; Fri, 23 Aug 2013 12:12:36 +0000 (UTC) Received: by mail-la0-f44.google.com with SMTP id eo20so419871lab.3 for ; Fri, 23 Aug 2013 05:12:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:newsgroups:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=GrME/9gpdIKS9OLal7SsZMmGtskhONsAHgUvi4rSY4U=; b=c5+wzu0RzitbEzQE2x75FJJOqYZvULeWhIupsOQAtOAmPaD49Grds4CS37YeFLwiau FFNj5J5mQh+WcjDqtR1CtPeE0Au6nO4A4xdd6FmjsqjSYPBBr4QdGK5dULzDb4Tjzu+f ZxQ4TJbu2mouAFnpD4e46JzegoROsxiPWdA9HzKz3yFidbxDgt9Q2n1m6mvXERzeXBGk 2KukSCJaBu1ZcoVGY0Ynmjs07rAs+vZE1LW9nT1o+XT0OQ4aXXs8IC6D/vHRoTxsNV/Q xhkFSI3b4cDrhumYjKkCp1QDx/9RJTapFKHn5lCZB12OxOxnHdqSU/WzNxKdacmJbs1p PRVw== X-Received: by 10.112.26.106 with SMTP id k10mr15655061lbg.27.1377259954401; Fri, 23 Aug 2013 05:12:34 -0700 (PDT) Received: from [192.168.1.128] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPSA id b6sm6596332lae.0.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Aug 2013 05:12:33 -0700 (PDT) Message-ID: <521751AF.6040905@gmail.com> Date: Fri, 23 Aug 2013 15:12:31 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130809 Thunderbird/17.0.8 MIME-Version: 1.0 Newsgroups: gmane.os.freebsd.current To: =?UTF-8?B?QmVybmhhcmQgRnLDtmhsaWNo?= Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: toolchain@freebsd.org, John-Mark Gurney , current@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 12:12:37 -0000 23.08.2013 12:58, Bernhard Fröhlich wrote: > I don't know if you are aware that IF you really do that we will have serious > problems to ship packages for 10. USE_GCC=any is the fallback in the > portstree for all ports that are unable to build with clang which was introduced > when HEAD switched to clang as default cc. Right now there are 150 ports in > the tree that use this fallback and quite a few of them are high profile ports: > > the highlights: > audio/nas devel/mingw32-binutils emulators/qemu emulators/virtualbox-ose > emulators/wine lang/go lang/v8 mail/courier math/fftw3 multimedia/libxine > multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 > security/clamav > > the full list: > http://dpaste.com/1354075/ > > A possible hack could be to add a check for USE_GCC=any to behave like > a USE_GCC=yes on HEAD on the affected platforms. This pulls in lang/gcc > from ports for a lot of people on HEAD I suppose. I object. Many ports that compiles perfectly on gcc 4.2.1 can't be compiled with lang/gcc. I checked this once and the number of ports that require strictly gcc 4.2.1 was bigger for me then number of ports that can't be compiled with clang but fill fine on lang/gcc. I'll gonna recheck whether lang/gcc42 is sufficient for them. But I have that bad feeling... -- Sphinx of black quartz, judge my vow. From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 12:17:07 2013 Return-Path: Delivered-To: freebsd-toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D5EB4EAC; Fri, 23 Aug 2013 12:17:07 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id DF80B22E3; Fri, 23 Aug 2013 12:17:06 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA28123; Fri, 23 Aug 2013 15:17:05 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1VCqIa-000PWl-U7; Fri, 23 Aug 2013 15:17:04 +0300 Message-ID: <52175288.4090500@FreeBSD.org> Date: Fri, 23 Aug 2013 15:16:08 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130810 Thunderbird/17.0.8 MIME-Version: 1.0 To: FreeBSD Current , freebsd-toolchain@FreeBSD.org Subject: stable/8 kernel-toolchain fails with clang on head X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 12:17:07 -0000 $ /usr/obj/usr/devel/svn/base/stable/8/make.amd64/make kernel-toolchain WITHOUT_CLANG=1 __MAKE_CONF=/dev/null SRCCONF=/dev/null ... cc -O2 -pipe -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/devel/svn/base/stable/8/tmp/usr\" -I/usr/obj/usr/devel/svn/base/stable/8/tmp/usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -I/usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/include -I/usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libcpp/include -I/usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libdecnumber -I/usr/obj/usr/devel/svn/base/stable/8/tmp/legacy/usr/include -DTARGET_NAME=\"amd64-undermydesk-freebsd\" -c /usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c In file included from /usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:58: /usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/output.h:123:6: warning: 'format' attribute argument not supported: __asm_fprintf__ [-Wignored-attributes] ATTRIBUTE_ASM_FPRINTF(2, 3); ^ /usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/output.h:113:53: note: expanded from macro 'ATTRIBUTE_ASM_FPRINTF' #define ATTRIBUTE_ASM_FPRINTF(m, n) __attribute__ ((__format__ (__asm_fprintf__, m, n))) ATTRIBUTE_NONNULL(m) ^ /usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:542:1: error: redefinition of a 'extern inline' function 'floor_log2' is not supported in C99 mode floor_log2 (unsigned HOST_WIDE_INT x) ^ /usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.h:174:1: note: previous definition is here floor_log2 (unsigned HOST_WIDE_INT x) ^ /usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:577:1: error: redefinition of a 'extern inline' function 'exact_log2' is not supported in C99 mode exact_log2 (unsigned HOST_WIDE_INT x) ^ /usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.h:180:1: note: previous definition is here exact_log2 (unsigned HOST_WIDE_INT x) ^ 1 warning and 2 errors generated. *** Error code 1 Stop in /usr/devel/svn/base/stable/8/gnu/usr.bin/cc/cc_int. It seems that the problem is specific to stable/8 and is caused by missing -std=gnu89. And that seems to be caused by -DNO_WARNS that is used for toolchain target. Dependency between NO_WARNS and CSTD was removed in r198335 + r198365, but those were never MFC-ed. What do you think? -- Andriy Gapon From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 12:26:53 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 75FE614B; Fri, 23 Aug 2013 12:26:53 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 00C212370; Fri, 23 Aug 2013 12:26:51 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA28175; Fri, 23 Aug 2013 15:26:50 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1VCqS1-000PXV-Vv; Fri, 23 Aug 2013 15:26:50 +0300 Message-ID: <521754E6.3030906@FreeBSD.org> Date: Fri, 23 Aug 2013 15:26:14 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130810 Thunderbird/17.0.8 MIME-Version: 1.0 To: David Chisnall Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: toolchain@FreeBSD.org, Julian Elischer , current@FreeBSD.org, "re@FreeBSD.org Engineering Team" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 12:26:53 -0000 on 23/08/2013 14:06 David Chisnall said the following: > Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in its > atomic generation so you can't use it sensibly without lots of inline > assembly (which it doesn't support for newer architectures) for > multithreaded things. > > Our libstdc++ is ancient and doesn't work with modern C++ codebases. On the other hand these tools are perfect for building FreeBSD kernel and base. Extrapolating my experience with base GCC I am very confident in it as a FreeBSD development tool. Extrapolating my experience with Clang I am not yet confident in it as a FreeBSD development tool. I do not care about C11, C++11 and modern C++ codebases. I care about what's in /usr/src and what gets compiled by buildkernel/buildworld. That's just me, of course. But, OTOH, those who care modern C++ codebases should be perfectly capable to install a compiler from ports or switch to clang as their default compiler. -- Andriy Gapon From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 12:30:05 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B75B03FA for ; Fri, 23 Aug 2013 12:30:05 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 65DB623C7 for ; Fri, 23 Aug 2013 12:30:05 +0000 (UTC) Received: by mail-oa0-f44.google.com with SMTP id l20so657440oag.3 for ; Fri, 23 Aug 2013 05:30:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=PHkkYJktgpAWS5S8TgXZ2OJ1HNVMu1h3SM3eHgbQ2Iw=; b=RWfG8Wd0P8bgzrgRRkHXs4iJGu4XLw/FR5DpMGTZG4AJDaLsopju13LpoOf31CVYYl /RmffvjwzC3WrXIx5OXFXBjkx/QXSiN0IcQloMdntHui1IkXlrxJmf3pQXmpOi5vur4k +H12cG+oNcrQCLcQu/Ijnd2Vk9LN9iPxFmoFs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=PHkkYJktgpAWS5S8TgXZ2OJ1HNVMu1h3SM3eHgbQ2Iw=; b=XuRhikmoY1EMwqX8i9FvM2ZfIIchTY7oJLNlAfBS2rm848DIFmWFTWnMtI1C0ONplu jyUb8fxNJaftJe+n0a0Dc5waC4H/THQvWqdNtA1vcuzMwuvePRJ+3ED/OsF/00KY7BE8 xauPcFZP1Aczf04vQ2I6HPoq2X6QIipwBq3FkbLnwjDuKk7XMVADYanTwCG6650o1azF S+UzC1SZepv28wwDTL8Z2gHmNLKRmQRAcCqoUahEoUZJ7FQ0WGXhojdn745dLF+gfIQb Ysmkhj+BRqjaEdESJ52Umiru8b+wrY1Hwvel6A5ictBftbwt+fhN4vbdMDmqOEoPtfYC JxZg== X-Gm-Message-State: ALoCoQkVqPztc3bj6LY9RbyKX5o32aQiTsvrgYOssbww1agDEutQbaug0cPnZS897qR2cA6i9T5v MIME-Version: 1.0 X-Received: by 10.60.96.131 with SMTP id ds3mr19970126oeb.50.1377261004641; Fri, 23 Aug 2013 05:30:04 -0700 (PDT) Sender: decke@bluelife.at Received: by 10.76.81.4 with HTTP; Fri, 23 Aug 2013 05:30:04 -0700 (PDT) X-Originating-IP: [80.123.233.199] In-Reply-To: <521751AF.6040905@gmail.com> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <521751AF.6040905@gmail.com> Date: Fri, 23 Aug 2013 14:30:04 +0200 X-Google-Sender-Auth: 4ZE8jCkaOytDbirNvPHfWCj8CbM Message-ID: Subject: Re: patch to add AES intrinsics to gcc From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= To: Volodymyr Kostyrko Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: toolchain@freebsd.org, John-Mark Gurney , current@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 12:30:05 -0000 On Fri, Aug 23, 2013 at 2:12 PM, Volodymyr Kostyrko wro= te: > 23.08.2013 12:58, Bernhard Fr=F6hlich wrote: >> >> I don't know if you are aware that IF you really do that we will have >> serious >> problems to ship packages for 10. USE_GCC=3Dany is the fallback in the >> portstree for all ports that are unable to build with clang which was >> introduced >> when HEAD switched to clang as default cc. Right now there are 150 ports >> in >> the tree that use this fallback and quite a few of them are high profile >> ports: >> >> the highlights: >> audio/nas devel/mingw32-binutils emulators/qemu emulators/virtualbox-ose >> emulators/wine lang/go lang/v8 mail/courier math/fftw3 multimedia/libxin= e >> multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 >> security/clamav >> >> the full list: >> http://dpaste.com/1354075/ >> >> A possible hack could be to add a check for USE_GCC=3Dany to behave like >> a USE_GCC=3Dyes on HEAD on the affected platforms. This pulls in lang/gc= c >> from ports for a lot of people on HEAD I suppose. > > > I object. Many ports that compiles perfectly on gcc 4.2.1 can't be compil= ed > with lang/gcc. I checked this once and the number of ports that require > strictly gcc 4.2.1 was bigger for me then number of ports that can't be > compiled with clang but fill fine on lang/gcc. > > I'll gonna recheck whether lang/gcc42 is sufficient for them. But I have > that bad feeling... lang/gcc42 is on the list of ports that have USE_GCC=3Dany. So you would ne= ed to fix it first to be able to compile it with clang 3.3 from base. We are not trying to build everything with lang/gcc but just the ports that= have USE_GCC=3Dany in their Makefile. Per default all ports are still build with= cc from base so clang 3.3 on HEAD. --=20 Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 12:30:24 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 346A75E1; Fri, 23 Aug 2013 12:30:24 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 036B923D5; Fri, 23 Aug 2013 12:30:23 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VCqVN-000BI1-H1; Fri, 23 Aug 2013 12:30:17 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r7NCUEgj047736; Fri, 23 Aug 2013 06:30:14 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX198vgJNMPScdGx8zzc2racG Subject: Re: patch to add AES intrinsics to gcc From: Ian Lepore To: David Chisnall In-Reply-To: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> Content-Type: text/plain; charset="us-ascii" Date: Fri, 23 Aug 2013 06:30:14 -0600 Message-ID: <1377261014.1111.43.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "re@FreeBSD.org Engineering Team" , current@FreeBSD.org, John-Mark Gurney , toolchain@FreeBSD.org, Julian Elischer X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 12:30:24 -0000 On Fri, 2013-08-23 at 12:06 +0100, David Chisnall wrote: > On 23 Aug 2013, at 11:42, Julian Elischer wrote: > > > no, I believe we have said that 10 would ship with clang by default. NO mention was made about gcc being absent, and I am uncomfortable with taking that step yet. Having gcc just present, will not hurt you.. even after it is gone we will need to support those who will be replacing clang with newer versions of gcc in hteir own products. > > The plan is not to delete gcc from the tree, it is to disable building gcc by default when clang is the system compiler. If you are building products then you are perfectly at liberty to set WITH_GCC=yes in your src.conf. > > Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in its atomic generation so you can't use it sensibly without lots of inline assembly (which it doesn't support for newer architectures) for multithreaded things. > > Our libstdc++ is ancient and doesn't work with modern C++ codebases. Putting them in the base system means that people will use them. If anyone wants them to remain, then speak now and this will be taken as your volunteering to: > > - Maintain our forks of both gcc and libstdc++ > - Handle every single PR that is filed by people using these > > If you are willing to do this, then that's great. If not, then you are asking other people to support ancient codebases that they are not using. > > David > I don't understand, you start by pointing out that gcc will still be in the tree and usable, then you go on to point out that it it won't be supported or maintained unless someone volunteers to do that, and you seem to be doing your best to discourage anyone from volunteering. Doesn't that sort of moot the point that the source isn't being deleted? -- Ian From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 12:34:18 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3DB4B871; Fri, 23 Aug 2013 12:34:18 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth3.wiscmail.wisc.edu (wmauth3.doit.wisc.edu [144.92.197.226]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0E8EE241A; Fri, 23 Aug 2013 12:34:17 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MRZ00G00GOO9R00@smtpauth3.wiscmail.wisc.edu>; Fri, 23 Aug 2013 07:34:16 -0500 (CDT) X-Spam-PmxInfo: Server=avs-3, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.8.23.122421, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from comporellon.tachypleus.net (adsl-76-208-67-185.dsl.mdsnwi.sbcglobal.net [76.208.67.185]) by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MRZ00I6JHL2MR00@smtpauth3.wiscmail.wisc.edu>; Fri, 23 Aug 2013 07:34:15 -0500 (CDT) Message-id: <521756C5.6050502@freebsd.org> Date: Fri, 23 Aug 2013 07:34:13 -0500 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130810 Thunderbird/17.0.8 To: Andriy Gapon Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <521754E6.3030906@FreeBSD.org> In-reply-to: <521754E6.3030906@FreeBSD.org> Cc: Julian Elischer , toolchain@FreeBSD.org, current@FreeBSD.org, "re@FreeBSD.org Engineering Team" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 12:34:18 -0000 On 08/23/13 07:26, Andriy Gapon wrote: > on 23/08/2013 14:06 David Chisnall said the following: >> Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in its >> atomic generation so you can't use it sensibly without lots of inline >> assembly (which it doesn't support for newer architectures) for >> multithreaded things. >> >> Our libstdc++ is ancient and doesn't work with modern C++ codebases. > On the other hand these tools are perfect for building FreeBSD kernel and base. > Extrapolating my experience with base GCC I am very confident in it as a > FreeBSD development tool. > Extrapolating my experience with Clang I am not yet confident in it as a > FreeBSD development tool. > This isn't even true. As CPUs gain new features, the set of available intrinsics gets more and more ancient, requiring ever more patching, workarounds, and #ifdef. Just look at the original subject of this thread! We're just talking about the default of a make.conf setting here. Switching to clang is a long-term goal of the project for good reason. Other vendors (Apple, for instance) have made the plunge first. This seems like as good a time as any to do it. And if it goes wrong somehow, we have lots of BETAs and it is trivial to change back at any time. -Nathan From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 12:56:17 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B9EC2FB5; Fri, 23 Aug 2013 12:56:17 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8457C2529; Fri, 23 Aug 2013 12:56:17 +0000 (UTC) Received: from c120.sec.cl.cam.ac.uk (c120.sec.cl.cam.ac.uk [128.232.18.120]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7NCuEDv054537 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 23 Aug 2013 12:56:15 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: patch to add AES intrinsics to gcc From: David Chisnall In-Reply-To: <521754E6.3030906@FreeBSD.org> Date: Fri, 23 Aug 2013 13:56:14 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <422728FC-CE88-4AEF-AD10-3BF8910A2109@FreeBSD.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <521754E6.3030906@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1508) Cc: toolchain@FreeBSD.org, "re@FreeBSD.org Engineering Team" , current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 12:56:17 -0000 On 23 Aug 2013, at 13:26, Andriy Gapon wrote: > On the other hand these tools are perfect for building FreeBSD kernel = and base. > Extrapolating my experience with base GCC I am very confident in it as = a > FreeBSD development tool. > Extrapolating my experience with Clang I am not yet confident in it as = a > FreeBSD development tool. Nathan has already dealt with this. > I do not care about C11, C++11 and modern C++ codebases. I care about = what's > in /usr/src and what gets compiled by buildkernel/buildworld. That's = just me, > of course. But, OTOH, those who care modern C++ codebases should be = perfectly > capable to install a compiler from ports or switch to clang as their = default > compiler. So you don't want a working debugger? Our gdb doesn't work at all on = MIPS and barely works with code compiled with clang or a recent gcc. We = are planning on importing LLDB soon (Ed Maste has been working on it, = funded by the FreeBSD Foundation), and it is a C++11 code base. It will = not build with our gcc or with our libstdc++ (and, in fact, since it = uses the LLVM libraries, will require LLVM in base to link libc++).=20 Or perhaps you don't care about flattened device trees. The device tree = compiler that we have in base is written in C++ and contains numerous = occurrences of ugly code to make it work with old compilers. I will be = very happy to remove a load of hacks once C++11 support is available in = the base system (not for 10.0, as dtc is used on a lot of tier 2 archs = where gcc is still default). David From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 12:59:37 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 555331DA; Fri, 23 Aug 2013 12:59:37 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A044A2551; Fri, 23 Aug 2013 12:59:35 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA28416; Fri, 23 Aug 2013 15:59:34 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1VCqxh-000PaQ-Md; Fri, 23 Aug 2013 15:59:33 +0300 Message-ID: <52175C7E.4050201@FreeBSD.org> Date: Fri, 23 Aug 2013 15:58:38 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130810 Thunderbird/17.0.8 MIME-Version: 1.0 To: Nathan Whitehorn Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <521754E6.3030906@FreeBSD.org> <521756C5.6050502@freebsd.org> In-Reply-To: <521756C5.6050502@freebsd.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Julian Elischer , toolchain@FreeBSD.org, current@FreeBSD.org, "re@FreeBSD.org Engineering Team" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 12:59:37 -0000 on 23/08/2013 15:34 Nathan Whitehorn said the following: > On 08/23/13 07:26, Andriy Gapon wrote: >> on 23/08/2013 14:06 David Chisnall said the following: >>> Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in its >>> atomic generation so you can't use it sensibly without lots of inline >>> assembly (which it doesn't support for newer architectures) for >>> multithreaded things. >>> >>> Our libstdc++ is ancient and doesn't work with modern C++ codebases. >> On the other hand these tools are perfect for building FreeBSD kernel and base. >> Extrapolating my experience with base GCC I am very confident in it as a >> FreeBSD development tool. >> Extrapolating my experience with Clang I am not yet confident in it as a >> FreeBSD development tool. >> > > This isn't even true. It's been true for me. > As CPUs gain new features, the set of available intrinsics > gets more and more ancient, requiring ever more patching, workarounds, and > #ifdef. Just look at the original subject of this thread! Yes. I am more comfortable with incremental changes. Bugs in those can be pinpointed quite easily and I do not affect those who don't use the new features. > We're just talking about the default of a make.conf setting here. Switching to > clang is a long-term goal of the project for good reason. I agree. > Other vendors (Apple, > for instance) have made the plunge first. This seems like as good a time as any > to do it. And if it goes wrong somehow, we have lots of BETAs and it is trivial > to change back at any time. I am totally comfortable with clang being default in head. I am also comfortable with gcc not being built by default in head. I am not yet comfortable with clang being default in a release. Even .0 one. JIMHO, it needs to age a little bit more. -- Andriy Gapon From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 13:04:34 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C9809391; Fri, 23 Aug 2013 13:04:34 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 839F325B8; Fri, 23 Aug 2013 13:04:33 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA28461; Fri, 23 Aug 2013 16:04:32 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1VCr2V-000Pb1-Mk; Fri, 23 Aug 2013 16:04:31 +0300 Message-ID: <52175DA7.7030908@FreeBSD.org> Date: Fri, 23 Aug 2013 16:03:35 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130810 Thunderbird/17.0.8 MIME-Version: 1.0 To: David Chisnall Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <521754E6.3030906@FreeBSD.org> <422728FC-CE88-4AEF-AD10-3BF8910A2109@FreeBSD.org> In-Reply-To: <422728FC-CE88-4AEF-AD10-3BF8910A2109@FreeBSD.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: toolchain@FreeBSD.org, "re@FreeBSD.org Engineering Team" , current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 13:04:34 -0000 on 23/08/2013 15:56 David Chisnall said the following: > So you don't want a working debugger? Our gdb doesn't work at all on MIPS > and barely works with code compiled with clang or a recent gcc. I am capable of using devel/gdb. Or do you mean kernel debugger? > We are > planning on importing LLDB soon (Ed Maste has been working on it, funded by > the FreeBSD Foundation), and it is a C++11 code base. It will not build with > our gcc or with our libstdc++ (and, in fact, since it uses the LLVM > libraries, will require LLVM in base to link libc++). There are multiple possible solutions to this issue. And note that I do support having clang in base and it being the default in head. > Or perhaps you don't care about flattened device trees. To be honest - no, I don't care about them. > The device tree > compiler that we have in base is written in C++ and contains numerous > occurrences of ugly code to make it work with old compilers. I will be very > happy to remove a load of hacks once C++11 support is available in the base > system (not for 10.0, as dtc is used on a lot of tier 2 archs where gcc is > still default). -- Andriy Gapon From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 13:05:38 2013 Return-Path: Delivered-To: freebsd-toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B1CE44D2; Fri, 23 Aug 2013 13:05:38 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 77F4E25CD; Fri, 23 Aug 2013 13:05:38 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::3c70:729f:ee6a:6ff6] (unknown [IPv6:2001:7b8:3a7:0:3c70:729f:ee6a:6ff6]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id C5AE65C43; Fri, 23 Aug 2013 15:05:34 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: stable/8 kernel-toolchain fails with clang on head From: Dimitry Andric In-Reply-To: <52175288.4090500@FreeBSD.org> Date: Fri, 23 Aug 2013 15:05:30 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <52175288.4090500@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1508) Cc: FreeBSD Current , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 13:05:38 -0000 On Aug 23, 2013, at 14:16, Andriy Gapon wrote: > $ /usr/obj/usr/devel/svn/base/stable/8/make.amd64/make = kernel-toolchain > WITHOUT_CLANG=3D1 __MAKE_CONF=3D/dev/null SRCCONF=3D/dev/null ... > It seems that the problem is specific to stable/8 and is caused by = missing > -std=3Dgnu89. And that seems to be caused by -DNO_WARNS that is used = for > toolchain target. > Dependency between NO_WARNS and CSTD was removed in r198335 + r198365, = but those > were never MFC-ed. >=20 > What do you think? Yes, I agree those should be MFC'd to stable/8. -Dimitry From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 13:38:02 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3B625661; Fri, 23 Aug 2013 13:38:02 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth2.wiscmail.wisc.edu (wmauth2.doit.wisc.edu [144.92.197.222]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0AB8727B0; Fri, 23 Aug 2013 13:38:01 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MRZ00E00HO64A00@smtpauth2.wiscmail.wisc.edu>; Fri, 23 Aug 2013 07:37:53 -0500 (CDT) X-Spam-PmxInfo: Server=avs-2, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.8.23.123017, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from comporellon.tachypleus.net (adsl-76-208-67-185.dsl.mdsnwi.sbcglobal.net [76.208.67.185]) by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MRZ001YKHR3TH00@smtpauth2.wiscmail.wisc.edu>; Fri, 23 Aug 2013 07:37:52 -0500 (CDT) Message-id: <5217579E.9000406@freebsd.org> Date: Fri, 23 Aug 2013 07:37:50 -0500 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130810 Thunderbird/17.0.8 To: Ian Lepore Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <1377261014.1111.43.camel@revolution.hippie.lan> In-reply-to: <1377261014.1111.43.camel@revolution.hippie.lan> Cc: "re@FreeBSD.org Engineering Team" , current@FreeBSD.org, John-Mark Gurney , toolchain@FreeBSD.org, Julian Elischer X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 13:38:02 -0000 On 08/23/13 07:30, Ian Lepore wrote: > On Fri, 2013-08-23 at 12:06 +0100, David Chisnall wrote: >> On 23 Aug 2013, at 11:42, Julian Elischer wrote: >> >>> no, I believe we have said that 10 would ship with clang by default. NO mention was made about gcc being absent, and I am uncomfortable with taking that step yet. Having gcc just present, will not hurt you.. even after it is gone we will need to support those who will be replacing clang with newer versions of gcc in hteir own products. >> The plan is not to delete gcc from the tree, it is to disable building gcc by default when clang is the system compiler. If you are building products then you are perfectly at liberty to set WITH_GCC=yes in your src.conf. >> >> Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in its atomic generation so you can't use it sensibly without lots of inline assembly (which it doesn't support for newer architectures) for multithreaded things. >> >> Our libstdc++ is ancient and doesn't work with modern C++ codebases. Putting them in the base system means that people will use them. If anyone wants them to remain, then speak now and this will be taken as your volunteering to: >> >> - Maintain our forks of both gcc and libstdc++ >> - Handle every single PR that is filed by people using these >> >> If you are willing to do this, then that's great. If not, then you are asking other people to support ancient codebases that they are not using. >> >> David >> > I don't understand, you start by pointing out that gcc will still be in > the tree and usable, then you go on to point out that it it won't be > supported or maintained unless someone volunteers to do that, and you > seem to be doing your best to discourage anyone from volunteering. > Doesn't that sort of moot the point that the source isn't being deleted? > It has to stay in the tree and usable -- at least for a while -- because not all of our Tier-2 platforms can build with clang yet. Those platforms, however, are typically not the ones that will require patching and maintenance (UltraSPARC 3s are not gaining any new features). I think that turning it off frees us during the 10.x release lifetime to actually remove it if the maintenance burden becomes too high -- or to revert our decision to turn it off at any time. Having it on by default locks us in to maintaining it for the lifetime of the branch. -Nathan From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 13:50:46 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E5897E93 for ; Fri, 23 Aug 2013 13:50:46 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B12182891 for ; Fri, 23 Aug 2013 13:50:46 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id s9so844918iec.35 for ; Fri, 23 Aug 2013 06:50:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=MzPYsY8mhizXky+GWWA9Ce9MhbFLVbpb5c2X44so0hk=; b=SaMOqAvFYd+brQkAs0Fl0y4snEaWOin57/5xLJH+eLqzcJ6J5uN23VIWluxIRGgAaf f2m+YLBm0f5b60JMzAnBs4F3+1p1fS8OfuHMARVSZl11R0ylhmeOzwiuSXq207bo1zcr d/Z4SEsroq+lANkec+pLkibgM/ZvTG4NdXA9PqionlXXGBsqucAr+e316n3CVpJQlxsj NXOPY0AtJBH/8bdnBAzO3+DBeYIPOT1D4a8q56ZiM8aN4XaLctqe3R1nuOGDfpV8t8Ef TrqG7xfkAskmPM4JtxZPvxjQvMnpWOFmVTSmUzBPTfQy4Bke+XmIfm7MroEPKohaFoWn Zasg== X-Gm-Message-State: ALoCoQlRax4cyDejpcwF6N8WjSWfOZpMosqY9fvYOQI6t2om06JN5c3FeKigSpavV99VvqD9j5u5 X-Received: by 10.43.68.130 with SMTP id xy2mr884864icb.41.1377265840671; Fri, 23 Aug 2013 06:50:40 -0700 (PDT) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id p5sm3030742igj.10.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Aug 2013 06:50:39 -0700 (PDT) Sender: Warner Losh Subject: Re: patch to add AES intrinsics to gcc Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Fri, 23 Aug 2013 07:50:38 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <9D48CB3D-E3FE-4189-9A6E-FE441C6854AB@bsdimp.com> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> To: David Chisnall X-Mailer: Apple Mail (2.1085) Cc: toolchain@FreeBSD.org, John-Mark Gurney , Julian Elischer , current@FreeBSD.org, "re@FreeBSD.org Engineering Team" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 13:50:47 -0000 On Aug 23, 2013, at 5:06 AM, David Chisnall wrote: > On 23 Aug 2013, at 11:42, Julian Elischer wrote: >=20 >> no, I believe we have said that 10 would ship with clang by default. = NO mention was made about gcc being absent, and I am uncomfortable with = taking that step yet. Having gcc just present, will not hurt you.. even = after it is gone we will need to support those who will be replacing = clang with newer versions of gcc in hteir own products. >=20 > The plan is not to delete gcc from the tree, it is to disable building = gcc by default when clang is the system compiler. If you are building = products then you are perfectly at liberty to set WITH_GCC=3Dyes in your = src.conf. >=20 > Our gcc is from 2007. It has no C11, no C++11 support. It has bugs = in its atomic generation so you can't use it sensibly without lots of = inline assembly (which it doesn't support for newer architectures) for = multithreaded things. >=20 > Our libstdc++ is ancient and doesn't work with modern C++ codebases. = Putting them in the base system means that people will use them. If = anyone wants them to remain, then speak now and this will be taken as = your volunteering to: >=20 > - Maintain our forks of both gcc and libstdc++ > - Handle every single PR that is filed by people using these >=20 > If you are willing to do this, then that's great. If not, then you = are asking other people to support ancient codebases that they are not = using. Well, it isn't quite that cut and dried. The date that gcc is from is not relevant. It works today for most of = the code out there. True, it doesn't have the latest features that a = small fraction of the code needs, but it works well enough. And it also = needs to be there for some upgrade paths. There's a use for gcc, and it = will likely be needed for these paths. As such, it has to work. Doesn't = matter if it is built by default or not, it simply has to keep working = as well as it has been working for the past 5 years to fill these roles. = For these tasks the nice C++ things simply don't matter or aren't = relevant. c11 features can't be put into the base for some time still = because of the issues on other architectures. We *HAVE* to have gcc on the other architectures. clang simply isn't = ready for MIPS, and has several outstanding problems on ARM. While work = is ongoing in these areas, clang simply won't be in as good a shape for = !x86 as it is for x86 in the 10.0 time frame. So even if gcc is turned off by default in 10 on x86, it still has to = work at least well enough to build the system and bootstrap clang. = Turning it off by default or on by default doesn't change this, and the = feature set that is used in 10 will basically be frozen soon, and the = non-x86 architectures will require the MI parts continue to work. I = don't see much decay that can happen in the x86MD parts that would break = it... Warner= From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 13:52:21 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CD24AFEB for ; Fri, 23 Aug 2013 13:52:21 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9B76228B0 for ; Fri, 23 Aug 2013 13:52:21 +0000 (UTC) Received: by mail-ie0-f181.google.com with SMTP id a14so846097iee.12 for ; Fri, 23 Aug 2013 06:52:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=DkpHDe2t7FBkYUkMdwcajD4L24Amp1X7+ZL5Una0Z2k=; b=ARsxvRMroxdIZjf4wvtqmrPXMqjsryy38V2MGoyuPUh8hEXEoxO9cGvXHMqpVSyfXb sf0fNVLcBvXFDAUyngFdWLQvefPu+kfNfeRgcXC0aN9udQoPR5KK24Y9RpBK0hck0TT8 J0i2fLyIeuvd1T+eOXNv/S1deU45Ra7Cw3h2X5G4lJvpp/7Huc7NEOE9ZH2hSzvnW2wr lqZxH3d7JGcemRmAhcwk0S1ouoFMi7HJSzWdHGUsxXZMw9Noz9+svu3cqVBLtXsowYsO njXZ4P6EMAY4FN3L1aQpZhtxyORZijpVVi79czR1XLAuErsBgZMPO677tghvz49G7n23 SKDA== X-Gm-Message-State: ALoCoQl6INJ4smTSaYzUtZuR93NaRIM68AHoJHCisPM3JDiyQKhrrY4WPGzcc/0f9j73q+DzMvhc X-Received: by 10.50.45.73 with SMTP id k9mr1620734igm.38.1377265935419; Fri, 23 Aug 2013 06:52:15 -0700 (PDT) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id b5sm3065418igm.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Aug 2013 06:52:14 -0700 (PDT) Sender: Warner Losh Subject: Re: GCC withdraw (was: Re: patch to add AES intrinsics to gcc) Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20130823111647.GT2951@home.opsec.eu> Date: Fri, 23 Aug 2013 07:52:13 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> To: Kurt Jaeger X-Mailer: Apple Mail (2.1085) Cc: toolchain@FreeBSD.org, current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 13:52:21 -0000 On Aug 23, 2013, at 5:16 AM, Kurt Jaeger wrote: > Hi! >=20 >>> I have a patch that I intend to commit before the 10.0 code >>> slush that removes GCC and libstdc++ from the default build on >>> platforms where clang is the system compiler. We definitely don't >>> want to be supporting our 6-year-old versions of these for the >>> lifetime of the 10.x branch. >>=20 >> Isn't it a POLA violation? >>=20 >> As for me I expect something like this: >> . 9.x gcc default and clang in base; >> . 10.x clang default and gcc in base; >> . 11.x gcc withdraw. >=20 > If the 150 ports that only work with gcc, all work with a ports > gcc and do not need the gcc from base, would the following be OK ? >=20 > - 9.x gcc default and clang in base; > - 10.x clang default and gcc in ports; No. That breaks non x86 architecutres. gcc must remain in base for now, = or there's no bootstrap ability. Nobody has done the lifting to cleanly = integrate gcc as a port into buildworld, althogh Brooks' work gets us = most of the way there. Warner From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 13:54:34 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5C2F472A; Fri, 23 Aug 2013 13:54:34 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0D4FF28FB; Fri, 23 Aug 2013 13:54:33 +0000 (UTC) Received: from c120.sec.cl.cam.ac.uk (c120.sec.cl.cam.ac.uk [128.232.18.120]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7NDsC3c082176 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 23 Aug 2013 13:54:14 GMT (envelope-from theraven@FreeBSD.org) Content-Type: multipart/signed; boundary="Apple-Mail=_BE8E92FE-C572-443D-BBCB-007C00543BDD"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: GCC withdraw (was: Re: patch to add AES intrinsics to gcc) From: David Chisnall In-Reply-To: Date: Fri, 23 Aug 2013 14:54:11 +0100 Message-Id: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> To: Warner Losh X-Mailer: Apple Mail (2.1508) Cc: toolchain@FreeBSD.org, Kurt Jaeger , current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 13:54:34 -0000 --Apple-Mail=_BE8E92FE-C572-443D-BBCB-007C00543BDD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 23 Aug 2013, at 14:52, Warner Losh wrote: > No. That breaks non x86 architecutres. gcc must remain in base for = now, or there's no bootstrap ability. Nobody has done the lifting to = cleanly integrate gcc as a port into buildworld, althogh Brooks' work = gets us most of the way there. We've been using brooks' work to build the base system with an = out-of-tree toolchain for some time now... David --Apple-Mail=_BE8E92FE-C572-443D-BBCB-007C00543BDD Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJSF2mEAAoJEKx65DEEsqIdhUEP/R7Uje7VNJYheAsQqad1D0ZN f4c/XdM/CvpfrCio/R9BDnClYYnvOxMW0fvQxiBRBdhwe7qx5/w/FEzD7No1XSpG bwQh5UY3na269wOw8t2EsmOlcRaWTa0QZGFtV/V6CUVgk3HwrRwZBT5pes3d8Q1J QF/U/ykd6o4Cl9aD3YdpAlMDDBwchdBE8Xw7eihWRsLYG2sQQDubjJq1N1mFu3cq fazcJOUzed3Y7uTxCJ2lToh2ycNhfIUuAE0fc9JXsMq647Ch5kIYpnuk74Z0A7V1 wkufNvviTzrzjMUfFv+B2cLScwn8NiBlVWwKc8H1RMOz4Ml+g9EotumBhZwoxnWC JdpSF6x7V11J869ijkjQO0PFrlvLXn26Da+mepSzC6SKUcdFD68u7578eafv8+9L /g6DswAa5NSbz1nRbadksQUC2Oa2bS0MXyOASWWk11ypbz0ldrvkQo5Ej6q1+7NT kcdwl7DqqKJjWWNQPLb4NoxLuyyGLjWDmrUpT6641gOOR3BaS0uwEo1yMNWb3XFv 9OVmj3xWs5QTLLtcKZ9KP0uvIjq2fkOfvujcdYAvtx8nT5eFv3YjiWeoxjF1Bvh1 to9tqF95MDWMEc7vOmcH73LwDYmjIfzARSVBGdGaXFmimX977j3vHtEkxH+6FbeW aHZ3pCnxiSVSowUgnbK5 =Zqcn -----END PGP SIGNATURE----- --Apple-Mail=_BE8E92FE-C572-443D-BBCB-007C00543BDD-- From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 13:54:47 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2EBF984F; Fri, 23 Aug 2013 13:54:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D650E2903; Fri, 23 Aug 2013 13:54:45 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id n12so580850wgh.24 for ; Fri, 23 Aug 2013 06:54:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=i1h0wGs9L9avCtKf5QdDzQDM1BJsfe8T3YYOSYXWg2Q=; b=BGEh+o9QO8LUW/TPdYG53rOMUuIdTo5zNaiPKF7X+3JFxqbVQ4d1Vhv2iWlR3Kiprv dfxeaHbOpAJ2SvX+ul7Bk3zkl0Hl1J6GYQaa6PTIf1iw2fhf4/xg3+scBF4T3EoAHsMT KT7HRX0fBjhigKem4Y2z8+pGaJVf2orruF3ndPsajP8iGVh8yPkCbNN3W0OyWZXAzkI8 dMhhoiZmENNN60NCnCDyUsRIpAeQqLjhTPJUq2nxfWYsQo15ECfV3abEY2gUFcSuSNm6 qpUitV4vcEKgDdFl2YqdU4RzBdYVPy4x6uCoVjM/eeWtx85ZktX+aVchulYNdtGZ7HDs 0DYw== MIME-Version: 1.0 X-Received: by 10.194.122.129 with SMTP id ls1mr1809538wjb.37.1377266084228; Fri, 23 Aug 2013 06:54:44 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.116.136 with HTTP; Fri, 23 Aug 2013 06:54:44 -0700 (PDT) In-Reply-To: <20130823114635.GB64913@zxy.spb.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <20130823114635.GB64913@zxy.spb.ru> Date: Fri, 23 Aug 2013 06:54:44 -0700 X-Google-Sender-Auth: TpN1h702denT-HSGus0oeUfMZz0 Message-ID: Subject: Re: patch to add AES intrinsics to gcc From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "re@FreeBSD.org Engineering Team" , "current@freebsd.org" , John-Mark Gurney , toolchain@freebsd.org, Julian Elischer X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 13:54:47 -0000 Hi! If firewire code doesn't build on clang correctly, have you filed a bug so it gets looked at before 10.0 is released? that's pretty broken code/behaviour. -adrian On 23 August 2013 04:46, Slawa Olhovchenkov wrote: > On Fri, Aug 23, 2013 at 06:42:21PM +0800, Julian Elischer wrote: > > > On 8/23/13 6:35 PM, David Chisnall wrote: > > > On 23 Aug 2013, at 10:58, Bernhard Fr?hlich wrote: > > > > > >> I don't know if you are aware that IF you really do that we will have > serious > > >> problems to ship packages for 10. USE_GCC=any is the fallback in the > > >> portstree for all ports that are unable to build with clang which was > introduced > > >> when HEAD switched to clang as default cc. Right now there are 150 > ports in > > >> the tree that use this fallback and quite a few of them are high > profile ports: > > >> > > >> the highlights: > > >> audio/nas devel/mingw32-binutils emulators/qemu > emulators/virtualbox-ose > > >> emulators/wine lang/go lang/v8 mail/courier math/fftw3 > multimedia/libxine > > >> multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 > > >> security/clamav > > >> > > >> the full list: > > >> http://dpaste.com/1354075/ > > >> > > >> A possible hack could be to add a check for USE_GCC=any to behave like > > >> a USE_GCC=yes on HEAD on the affected platforms. This pulls in > lang/gcc > > >> from ports for a lot of people on HEAD I suppose. > > >> > > >> We certainly need to do that switch to remove the ancient gcc from > base > > >> some time but with my portmgr hat on I can only say we don't plan to > do that > > >> before 10.0 especially not if we are only talking about a few weeks > time window. > > > That is unfortunate. We have said for over a year that 10.0 should > not ship with gcc. I can delay committing the patch to flip the switch > until later in the code slush, if re approves, but ports that require gcc > should be building with gcc from ports (which will also improve code > quality, as gcc 4.6/7 produce significantly better code than 4.2.1). > > no, I believe we have said that 10 would ship with clang by default. > > 10 from this winner have broken firewire code when building by clang > -- cannot resume from sleep. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 13:55:43 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 574B2998 for ; Fri, 23 Aug 2013 13:55:43 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1F1DA2923 for ; Fri, 23 Aug 2013 13:55:42 +0000 (UTC) Received: by mail-ie0-f180.google.com with SMTP id x14so846092ief.11 for ; Fri, 23 Aug 2013 06:55:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=JN4dJtjd07jauEc8cJ1vL6784Jannesp7AMElStjHJY=; b=kjavquz/z2bRs1KqKQZ2HvvDhr2QN7wyOw1hChmkfUhwEbPHnt3Vjm6uusl2dbU6Hz kwxV24kzMrqD2vlzVo+DdHHZcnTCtj0HDVrBBHM4JHclc8P1PQEEN8sha4AcNxQ5DNGx dtmPperROH9BpYhRVj/hWgBusZLSWlhEqlnC6rPknJPwql7LlL7cPWwB+vHYbUDUqA9S fn1m0G1gHgkG1jHjDsWw5OrIB0SO+OLLJHWN2WRAlwjWWhg0Codylm701HFZftbP8S0y e52wN/yM6s+krjmd5NgDMynhGtnLxvWyv8j5lxRq7GgNrL3Xj+v45TryYqbfKO9SzJ/y zfEA== X-Gm-Message-State: ALoCoQlvKkiBxNl+6WKmr/H01PXt/TcM1sxhGHHoow87z5eksgbqedCByc7rK5NvSCXwaPQt0XA0 X-Received: by 10.43.66.11 with SMTP id xo11mr1362127icb.21.1377266142281; Fri, 23 Aug 2013 06:55:42 -0700 (PDT) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id cl4sm52085igc.1.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Aug 2013 06:55:41 -0700 (PDT) Sender: Warner Losh Subject: Re: patch to add AES intrinsics to gcc Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <1377261014.1111.43.camel@revolution.hippie.lan> Date: Fri, 23 Aug 2013 07:55:40 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <1377261014.1111.43.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1085) Cc: "re@FreeBSD.org Engineering Team" , current@FreeBSD.org, John-Mark Gurney , toolchain@FreeBSD.org, Julian Elischer X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 13:55:43 -0000 On Aug 23, 2013, at 6:30 AM, Ian Lepore wrote: > On Fri, 2013-08-23 at 12:06 +0100, David Chisnall wrote: >> On 23 Aug 2013, at 11:42, Julian Elischer wrote: >>=20 >>> no, I believe we have said that 10 would ship with clang by default. = NO mention was made about gcc being absent, and I am uncomfortable with = taking that step yet. Having gcc just present, will not hurt you.. even = after it is gone we will need to support those who will be replacing = clang with newer versions of gcc in hteir own products. >>=20 >> The plan is not to delete gcc from the tree, it is to disable = building gcc by default when clang is the system compiler. If you are = building products then you are perfectly at liberty to set WITH_GCC=3Dyes = in your src.conf. >>=20 >> Our gcc is from 2007. It has no C11, no C++11 support. It has bugs = in its atomic generation so you can't use it sensibly without lots of = inline assembly (which it doesn't support for newer architectures) for = multithreaded things. >>=20 >> Our libstdc++ is ancient and doesn't work with modern C++ codebases. = Putting them in the base system means that people will use them. If = anyone wants them to remain, then speak now and this will be taken as = your volunteering to: >>=20 >> - Maintain our forks of both gcc and libstdc++ >> - Handle every single PR that is filed by people using these >>=20 >> If you are willing to do this, then that's great. If not, then you = are asking other people to support ancient codebases that they are not = using. >>=20 >> David >>=20 >=20 > I don't understand, you start by pointing out that gcc will still be = in > the tree and usable, then you go on to point out that it it won't be > supported or maintained unless someone volunteers to do that, and you > seem to be doing your best to discourage anyone from volunteering. > Doesn't that sort of moot the point that the source isn't being = deleted? If it is in the tree it's gotta work. And it has to be in the tree for = !x86 architectures. So on or off for x86 doesn't really add to the load = at all, and the C++/C11 stuff is a red herring. If it isn't cc, then = people wanting clang by default won't care... And besides, ports aren't completely ready to kill it, so it has to work = for them. Warner= From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 13:59:13 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E94B7C98 for ; Fri, 23 Aug 2013 13:59:13 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B69352955 for ; Fri, 23 Aug 2013 13:59:13 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id c10so861834ieb.17 for ; Fri, 23 Aug 2013 06:59:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=oH9fxsHTsgyKyxiDvk/IxgApeVfXxHNlUlxHjMK+5Gw=; b=lE/902H+FdBg1qUMT4cVsZj9Se9Dv9JXtx6bWJZWGlHb0V2tQygKKqSOtZRtSXsSCe 8KiJhvHnUhEer/WqEzTEek4NwxHODFbKuIJlV2HVDAwpwBhJ7iBqC07WcOs10YrDsGbF mvUmnm1dYMR5jGV+r4Cr6x2iTyEca39JN2TckGvYXuavYJIu8LR5astw931SKVB/FAMS Kg5SFYo0Y4OKgEbXg8yk+biCRUxrQuVAPsUPAFI2wkILUdwbTBPSZv01IVrlpbzlY/uB mTG2AvQFCOp8GCiWxFvHrqKdHfb9ULYFyvJJhdVae3OMxfOgcpfsrHzhLKAaLpNJqpjl YIDQ== X-Gm-Message-State: ALoCoQl0ak/S99N92Ee5yYX841tO8egEQ9uOv/OxZ9SMjrB99+D7jhhvYUrMW5ntRX/S7dA7x+cE X-Received: by 10.50.131.170 with SMTP id on10mr1653417igb.12.1377266353233; Fri, 23 Aug 2013 06:59:13 -0700 (PDT) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id g5sm3078609igc.9.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Aug 2013 06:59:12 -0700 (PDT) Sender: Warner Losh Subject: Re: GCC withdraw (was: Re: patch to add AES intrinsics to gcc) Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Fri, 23 Aug 2013 07:59:11 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <04A68472-3377-4E48-B7BE-DDBF070507B4@bsdimp.com> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> To: David Chisnall X-Mailer: Apple Mail (2.1085) Cc: toolchain@FreeBSD.org, Kurt Jaeger , current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 13:59:14 -0000 On Aug 23, 2013, at 7:54 AM, David Chisnall wrote: > On 23 Aug 2013, at 14:52, Warner Losh wrote: >> No. That breaks non x86 architecutres. gcc must remain in base for = now, or there's no bootstrap ability. Nobody has done the lifting to = cleanly integrate gcc as a port into buildworld, althogh Brooks' work = gets us most of the way there. >=20 > We've been using brooks' work to build the base system with an = out-of-tree toolchain for some time now... I'll have to try the native build part of the cycle then... Early = versions of the patch failed when you cross built the target, installed = the target, but wound up with no compilers to bootstrap the external = toolchains with to do native builds on the target. Warner From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 15:16:26 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3B38220A; Fri, 23 Aug 2013 15:16:26 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1A21E2DEB; Fri, 23 Aug 2013 15:16:26 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id r7NFGMFf047082; Fri, 23 Aug 2013 08:16:22 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id r7NFGMZ8047081; Fri, 23 Aug 2013 08:16:22 -0700 (PDT) (envelope-from sgk) Date: Fri, 23 Aug 2013 08:16:22 -0700 From: Steve Kargl To: Boris Samorodov Subject: Re: GCC withdraw (was: Re: patch to add AES intrinsics to gcc) Message-ID: <20130823151622.GA46958@troutmask.apl.washington.edu> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5217413A.9080105@passap.ru> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: toolchain@FreeBSD.org, John-Mark Gurney , current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 15:16:26 -0000 On Fri, Aug 23, 2013 at 03:02:18PM +0400, Boris Samorodov wrote: > 23.08.2013 13:16, David Chisnall ??????????: > >> I have a patch that I intend to commit before the 10.0 code >> slush that removes GCC and libstdc++ from the default build >> on platforms where clang is the system compiler. We definitely >> don't want to be supporting our 6-year-old versions of these >> for the lifetime of the 10.x branch. > > Isn't it a POLA violation? > > As for me I expect something like this: > . 9.x gcc default and clang in base; > . 10.x clang default and gcc in base; > . 11.x gcc withdraw. > +1 -- Steve From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 16:36:52 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0AAE299E for ; Fri, 23 Aug 2013 16:36:52 +0000 (UTC) (envelope-from mueller6724@bellsouth.net) Received: from nm16-vm3.access.bullet.mail.bf1.yahoo.com (nm16-vm3.access.bullet.mail.bf1.yahoo.com [216.109.115.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 590FD22C5 for ; Fri, 23 Aug 2013 16:36:51 +0000 (UTC) Received: from [66.196.81.166] by nm16.access.bullet.mail.bf1.yahoo.com with NNFMP; 23 Aug 2013 16:31:31 -0000 Received: from [98.139.221.52] by tm12.access.bullet.mail.bf1.yahoo.com with NNFMP; 23 Aug 2013 16:31:30 -0000 Received: from [127.0.0.1] by smtp105.sbc.mail.bf1.yahoo.com with NNFMP; 23 Aug 2013 16:31:30 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bellsouth.net; s=s1024; t=1377275490; bh=aHxjQaf1iaROsi2Y8HOhm5EqSXl6Bp5fmBb1N2u7Xf8=; h=X-Yahoo-Newman-Id:Message-ID:Date:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:CC:Subject; b=nV/Sjw85iLOnPVd3aBw0oHCsPP5aT2xO0/vwKmvXWpKtYiXQCgdrK+CpNEnTQJGh6U0N3yUjrfr2BVpEyLTf38S2vLtBwgDPx6aPFAPmhKvEsLchtIag6VoIJffjbxTrjqcwdn/sGRyKADKWoLqUsUS17RFLZNrMWj3VFyquJrY= X-Yahoo-Newman-Id: 684272.3945.bm@smtp105.sbc.mail.bf1.yahoo.com Message-ID: <684272.3945.bm@smtp105.sbc.mail.bf1.yahoo.com> Date: Fri, 23 Aug 2013 09:31:30 -0700 (PDT) X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 9xhoO_AVM1nAS3Cm_vgVVkQYpYj7LJW_0bm9MDc7A1HWDjQ FFHGVfJh0Dtb.sHSl3jIaAL2F7Q8vuJKsdjTUuZ8OBaUgQCInDaxIV6jD4Sg VDRtgBgZ1z7I2HHBfRt5wo31uTqYARaEr4I9Uc2p36OGUg9PGyOEBy4veIeO YbAoob2iFh467UmEB6S8gG5ual4sP_O4VtEjfB7bdU6xNr0TjeS5LcHEe_UT r9KYiGCGvs0gAPj_6IntGPg6cJN.ihXfCcX512rDgUnnJb1CrCX5EFyBHHNe EKTcChnDuAJhOzXWFZg1D1ShCAsekkgtrQfXvs9RnlsEfvbkc7G9tmCegXgx yGTrjiRXdQU1bxfzzYIW0imu1dj6qJPV7Gj2wKYQnpK4iuIMcLSCCB5xImZy w.k.0brV_6WvRQa0cKIMQSsv6rgzCAp46H_f_p275C0f7Koe_97J..oAzzdC pY9PkST6AVa6pN0fP_vGI6Xv8JOPWSv2FbmUxjkEANYoAnUEvm4VRANgOlFW IaErzZC_LyGP2CI_0lakuSX_f65OFshhMz3QyTYA68j6lnTUNkjWGjSpCLWe 2CN90ZMCG X-Yahoo-SMTP: Kz_aW1.swBBYof3zAD7.RWzXz9ZAQVDMml1VADsbgPT4Kq79LC0- X-Rocket-Received: from localhost (mueller6724@74.130.200.176 with plain) by smtp105.sbc.mail.bf1.yahoo.com with SMTP; 23 Aug 2013 09:31:30 -0700 PDT From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: GCC withdraw (was: Re: patch to add AES intrinsics to gcc) Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 16:36:52 -0000 > As for me I expect something like this: > . 9.x gcc default and clang in base; > . 10.x clang default and gcc in base; > . 11.x gcc withdraw. There is also the concern whether clang in base will reliably build gcc required for some ports, and then there are those CPU architectures for which clang is nonexistent or not ready. Regarding those ports that build with the ancient gcc 4.2.1 but not with newer versions, that has to be considered a bug. Consider that Linux and the other BSDs use newer versions of gcc to build their base system and ports or pkgsrc. Tom From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 18:17:42 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 797493B0; Fri, 23 Aug 2013 18:17:42 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 468B52910; Fri, 23 Aug 2013 18:17:42 +0000 (UTC) Received: from Julian-MBP3.local (etroy.elischer.org [121.45.226.51]) (authenticated bits=0) by vps1.elischer.org (8.14.6/8.14.6) with ESMTP id r7NIHabb001677 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 23 Aug 2013 11:17:39 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <5217A73A.7090402@freebsd.org> Date: Sat, 24 Aug 2013 02:17:30 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Andriy Gapon Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <521754E6.3030906@FreeBSD.org> In-Reply-To: <521754E6.3030906@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: toolchain@FreeBSD.org, current@FreeBSD.org, "re@FreeBSD.org Engineering Team" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 18:17:42 -0000 On 8/23/13 8:26 PM, Andriy Gapon wrote: > on 23/08/2013 14:06 David Chisnall said the following: >> Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in its >> atomic generation so you can't use it sensibly without lots of inline >> assembly (which it doesn't support for newer architectures) for >> multithreaded things. >> >> Our libstdc++ is ancient and doesn't work with modern C++ codebases. > On the other hand these tools are perfect for building FreeBSD kernel and base. > Extrapolating my experience with base GCC I am very confident in it as a > FreeBSD development tool. > Extrapolating my experience with Clang I am not yet confident in it as a > FreeBSD development tool. > > I do not care about C11, C++11 and modern C++ codebases. I care about what's > in /usr/src and what gets compiled by buildkernel/buildworld. That's just me, > of course. But, OTOH, those who care modern C++ codebases should be perfectly > capable to install a compiler from ports or switch to clang as their default > compiler. > +1 I'd like to see it still be "there if you need it" in 10 in 11 it's in ports From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 18:21:00 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 310C06BA; Fri, 23 Aug 2013 18:21:00 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 021E92981; Fri, 23 Aug 2013 18:20:59 +0000 (UTC) Received: from Julian-MBP3.local (etroy.elischer.org [121.45.226.51]) (authenticated bits=0) by vps1.elischer.org (8.14.6/8.14.6) with ESMTP id r7NIKDr5001682 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 23 Aug 2013 11:20:16 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <5217A7D8.1030806@freebsd.org> Date: Sat, 24 Aug 2013 02:20:08 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Poul-Henning Kamp Subject: Re: GCC withdraw References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <52174D51.2050601@digsys.bg> <21414.1377258940@critter.freebsd.dk> In-Reply-To: <21414.1377258940@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: toolchain@FreeBSD.org, Kurt Jaeger , current@FreeBSD.org, Daniel Kalchev X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 18:21:00 -0000 On 8/23/13 7:55 PM, Poul-Henning Kamp wrote: > In message <52174D51.2050601@digsys.bg>, Daniel Kalchev writes: > >>> - 9.x gcc default and clang in base; >>> - 10.x clang default and gcc in ports; >> I believe this is the best idea so far. As long as these ports work with >> gcc in ports, that is. > +1 > well as I was forced to go back to gcc to get a compiling & running kernel on my VPS (xen) I'm not convinced that clang is there yet. I'd be really grumpy if I had to go through al the ports hoopla to recompile my kernel. From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 21:03:07 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D6868FFB; Fri, 23 Aug 2013 21:03:07 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 8FFBC240B; Fri, 23 Aug 2013 21:03:07 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VCyXh-000Ayg-FX; Sat, 24 Aug 2013 01:05:13 +0400 Date: Sat, 24 Aug 2013 01:05:13 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: patch to add AES intrinsics to gcc Message-ID: <20130823210513.GA3796@zxy.spb.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <20130823114635.GB64913@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: "re@FreeBSD.org Engineering Team" , "current@freebsd.org" , John-Mark Gurney , toolchain@freebsd.org, Julian Elischer X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 21:03:07 -0000 On Fri, Aug 23, 2013 at 06:54:44AM -0700, Adrian Chadd wrote: > Hi! > > If firewire code doesn't build on clang correctly, have you filed a bug so > it gets looked at before 10.0 is released? that's pretty broken > code/behaviour. How I can do it correctly? Currently in src.conf: WITHOUT_CLANG=yes WITHOUT_CLANG_IS_CC=yes Need recompile world? System build from sources Jun 8. clang -- Jan 9. From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 22:01:16 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3F756DA7; Fri, 23 Aug 2013 22:01:16 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 2722C273D; Fri, 23 Aug 2013 22:01:15 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-67-180-208-218.hsd1.ca.comcast.net [67.180.208.218]) by elvis.mu.org (Postfix) with ESMTPSA id A76DB1A3E0F; Fri, 23 Aug 2013 15:01:15 -0700 (PDT) Message-ID: <5217DBAB.5030607@freebsd.org> Date: Fri, 23 Aug 2013 15:01:15 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: David Chisnall Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> In-Reply-To: <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: toolchain@FreeBSD.org, John-Mark Gurney , current@FreeBSD.org, "re@FreeBSD.org Engineering Team" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 22:01:16 -0000 On 8/23/13 3:35 AM, David Chisnall wrote: > On 23 Aug 2013, at 10:58, Bernhard Fröhlich wrote: > >> I don't know if you are aware that IF you really do that we will have serious >> problems to ship packages for 10. USE_GCC=any is the fallback in the >> portstree for all ports that are unable to build with clang which was introduced >> when HEAD switched to clang as default cc. Right now there are 150 ports in >> the tree that use this fallback and quite a few of them are high profile ports: >> >> the highlights: >> audio/nas devel/mingw32-binutils emulators/qemu emulators/virtualbox-ose >> emulators/wine lang/go lang/v8 mail/courier math/fftw3 multimedia/libxine >> multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 >> security/clamav >> >> the full list: >> http://dpaste.com/1354075/ >> >> A possible hack could be to add a check for USE_GCC=any to behave like >> a USE_GCC=yes on HEAD on the affected platforms. This pulls in lang/gcc >> from ports for a lot of people on HEAD I suppose. >> >> We certainly need to do that switch to remove the ancient gcc from base >> some time but with my portmgr hat on I can only say we don't plan to do that >> before 10.0 especially not if we are only talking about a few weeks time window. > That is unfortunate. We have said for over a year that 10.0 should not ship with gcc. I can delay committing the patch to flip the switch until later in the code slush, if re approves, but ports that require gcc should be building with gcc from ports (which will also improve code quality, as gcc 4.6/7 produce significantly better code than 4.2.1). > > David > > _______________________________________________ > Why can't ports just then add the old-version of GCC? This tight coupling between src and ports is screwing us over for far too long. If src needs to move on, and it surely seems like it does, then ports needs to adapt. No offense to either team, but this is just common sense. From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 22:38:01 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3A4166E8 for ; Fri, 23 Aug 2013 22:38:01 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F24C22944 for ; Fri, 23 Aug 2013 22:38:00 +0000 (UTC) Received: by mail-ob0-f169.google.com with SMTP id wc20so1279159obb.28 for ; Fri, 23 Aug 2013 15:37:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=fCa96hHT09vZYKsMml2pu3r0dMr5x18tp0uOx0IG7Ys=; b=OL/D2/nCu+Uf6Dtl6/Iu0uyPZxpmyIGyP4Kn2afqrgojKqdcnl5D0uajrS5BVxg1h6 GY+090LKxYPPT7LzH2aUFtsSvzOqrgvJ7gcHyZrdF105stHXh+RbJKhBy5yVsuKHp6+Q e1qQjKCnG2a4M++qnPUZg/ETwAsa4NvxXx+tUtJ3twnObD9H8mMYMWqQzdRNUYXzFpE8 20uNrpEylSJ8Wl7W9jjX6+GwZMezT7kBkTV8VEVzk806LwgHZBg8qyXiNtguxAVPXpEP eNQGxY/guY+J/fq18j5xzfMDqCgxoUO4Hyg5q/f7cDGto8dppBWfLFuDzVR9+wNWHeCu P+Dg== X-Gm-Message-State: ALoCoQmWT06/2jsMi1VxVtaN2mfPJeJWOmzLaU92DSbl9jHjZfxU67DpE/ZKVpeNltwImPu/VqSv X-Received: by 10.60.124.14 with SMTP id me14mr1745298oeb.4.1377297474066; Fri, 23 Aug 2013 15:37:54 -0700 (PDT) Received: from monkey-bot.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id qi5sm2052749obb.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Aug 2013 15:37:53 -0700 (PDT) Sender: Warner Losh Subject: Re: patch to add AES intrinsics to gcc Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=iso-8859-1 From: Warner Losh In-Reply-To: <5217DBAB.5030607@freebsd.org> Date: Fri, 23 Aug 2013 16:37:50 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <86032E72-A569-4946-B4F8-26F687067B31@bsdimp.com> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <5217DBAB.5030607@freebsd.org> To: Alfred Perlstein X-Mailer: Apple Mail (2.1085) Cc: toolchain@FreeBSD.org, John-Mark Gurney , current@FreeBSD.org, "re@FreeBSD.org Engineering Team" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 22:38:01 -0000 On Aug 23, 2013, at 4:01 PM, Alfred Perlstein wrote: > On 8/23/13 3:35 AM, David Chisnall wrote: >> On 23 Aug 2013, at 10:58, Bernhard Fr=F6hlich = wrote: >>=20 >>> I don't know if you are aware that IF you really do that we will = have serious >>> problems to ship packages for 10. USE_GCC=3Dany is the fallback in = the >>> portstree for all ports that are unable to build with clang which = was introduced >>> when HEAD switched to clang as default cc. Right now there are 150 = ports in >>> the tree that use this fallback and quite a few of them are high = profile ports: >>>=20 >>> the highlights: >>> audio/nas devel/mingw32-binutils emulators/qemu = emulators/virtualbox-ose >>> emulators/wine lang/go lang/v8 mail/courier math/fftw3 = multimedia/libxine >>> multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 >>> security/clamav >>>=20 >>> the full list: >>> http://dpaste.com/1354075/ >>>=20 >>> A possible hack could be to add a check for USE_GCC=3Dany to behave = like >>> a USE_GCC=3Dyes on HEAD on the affected platforms. This pulls in = lang/gcc >>> from ports for a lot of people on HEAD I suppose. >>>=20 >>> We certainly need to do that switch to remove the ancient gcc from = base >>> some time but with my portmgr hat on I can only say we don't plan to = do that >>> before 10.0 especially not if we are only talking about a few weeks = time window. >> That is unfortunate. We have said for over a year that 10.0 should = not ship with gcc. I can delay committing the patch to flip the switch = until later in the code slush, if re approves, but ports that require = gcc should be building with gcc from ports (which will also improve code = quality, as gcc 4.6/7 produce significantly better code than 4.2.1). >>=20 >> David >>=20 >> _______________________________________________ >>=20 > Why can't ports just then add the old-version of GCC? This tight = coupling between src and ports is screwing us over for far too long. ports already has various gcc versions in ports, needed for dozens of = ports that require newer gcc, and this could be adopted for the gcc from = base issue. But that's not the issue. It is making the ports that need = it use it, and from the quoted message it sounds like that would take = work. Work takes time, and the window is closing. > If src needs to move on, and it surely seems like it does, then ports = needs to adapt. I'd dispute the 'and surely it seems like it does' part of this. Non x86 = architectures will continue to use gcc because clang just isn't ready at = this time for them. Some are very close (arm), some are close = (powerpc64, mips*), some are no where near ready, or will never be ready = (sparc64, ia64). There's no coherent, documented plan for these absent = gcc at the moment. There are lots of pieces there, and those pieces will = form the basis of the solution (+handbook updates) for the removal of = gcc in 11, but we just aren't there yet. > No offense to either team, but this is just common sense. The only ones that would really matter are ones in any bootstrap path we = might need for external toolchains. Since qemu is the basis for cross = building ports, it is disturbing to see that on the list. I know qemu = has, in the past, been sensitive to compiler versions, as are many of = the emulators in the tree. It might not be a simple matter to just use = gcc 4.6 or 4.7 for some of the items on the list. When I've moved gcc = versions and had problems with FOSS it is either due to new = warnings/errors and language violations. Some of these are trivial to = fix, others reveal fundamental flaws in the code and many changes are = needed. Sometimes newer compilers also have optimizations bugs (as = opposed to language violations now optimized differently) which break = things at run-time, despite things appearing to compile. These aren't = insurmountable problems, but do take time to implement and test. Warner From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 09:46:37 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3E867FAB; Sat, 24 Aug 2013 09:46:37 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0A71924CC; Sat, 24 Aug 2013 09:46:36 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7O9kXPe008896 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 24 Aug 2013 09:46:34 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: patch to add AES intrinsics to gcc From: David Chisnall In-Reply-To: Date: Sat, 24 Aug 2013 10:46:29 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <7D444AD2-D5DD-4F3A-BF43-720D68009657@FreeBSD.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <521751AF.6040905@gmail.com> To: =?iso-8859-1?Q?Bernhard_Fr=F6hlich?= X-Mailer: Apple Mail (2.1508) Cc: toolchain@FreeBSD.org, Volodymyr Kostyrko , John-Mark Gurney , current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 09:46:37 -0000 On 23 Aug 2013, at 13:30, Bernhard Fr=F6hlich wrote: > lang/gcc42 is on the list of ports that have USE_GCC=3Dany. So you = would need > to fix it first to be able to compile it with clang 3.3 from base. What is the issue with the gcc 4.2.1 build (aside from the fact that it = has a terrifying number of warnings when built with any recent = compiler)? The gcc 4.2.1 in base builds with clang - that's how we = currently build it in head... David From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 10:05:25 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8817259A; Sat, 24 Aug 2013 10:05:25 +0000 (UTC) (envelope-from theraven@freebsd.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 50345258B; Sat, 24 Aug 2013 10:05:24 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7OA5KEV009048 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 24 Aug 2013 10:05:21 GMT (envelope-from theraven@freebsd.org) Content-Type: multipart/signed; boundary="Apple-Mail=_69A682A3-CBD1-4732-B617-BCAE64BAB327"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: patch to add AES intrinsics to gcc From: David Chisnall In-Reply-To: <86032E72-A569-4946-B4F8-26F687067B31@bsdimp.com> Date: Sat, 24 Aug 2013 11:05:15 +0100 Message-Id: <1380949A-254A-4222-BEDE-0C23E16E4F67@freebsd.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <5217DBAB.5030607@freebsd.org> <86032E72-A569-4946-B4F8-26F687067B31@bsdimp.com> To: Warner Losh X-Mailer: Apple Mail (2.1508) Cc: toolchain@freebsd.org, John-Mark Gurney , Alfred Perlstein , "re@FreeBSD.org Engineering Team" , current@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 10:05:25 -0000 --Apple-Mail=_69A682A3-CBD1-4732-B617-BCAE64BAB327 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 23 Aug 2013, at 23:37, Warner Losh wrote: > I'd dispute the 'and surely it seems like it does' part of this. Non = x86 architectures will continue to use gcc because clang just isn't = ready at this time for them. Some are very close (arm), some are close = (powerpc64, mips*), some are no where near ready, or will never be ready = (sparc64, ia64). There's no coherent, documented plan for these absent = gcc at the moment. There are lots of pieces there, and those pieces will = form the basis of the solution (+handbook updates) for the removal of = gcc in 11, but we just aren't there yet. The plan, which has been discussed on mailing lists, on IRC, and at = DevSummits is for tier 2 ports to depend on an external toolchain. For = those vendors that are not prevented from using GPLv3 compilers, this = means that they will be able to take advantage of, for example, the = significant improvements to the MIPS and PowerPC back ends that gcc has = had over the last 6 years. For everyone else, it will mean installing a = compiler from ports. For now, tier 2 architectures will continue to build a toolchain from = the src tree and use that. By 11.0, gcc will be gone from the base = system and they will be required to use something external if they are = not supported by clang. Brooks has been working hard on making this = easy, and it is generally an improvement for cross-building embedded = systems as the cross-compile toolchain is no longer rebuilt every time = you change a file in the kernel, resulting in faster builds. It is also = easier to use toolchains provided by chip vendors, which is something = that MIPS and ARM vendors have been asking for for a very long time. =20 For x86 and ARMv6/7, Clang has been the default compiler for a long time = and gcc has been increasingly problematic (for example, our gcc does not = support ARM EABI, which will be the default in 10.0 for ARMv6 and later, = so if you want to build for a modern ARM chip then you need either clang = or a more recent gcc than we ship). Claiming that this is something = done at the expense of non-x86 architectures is highly misleading, as = improving ARM support is one of the driving factors behind the switch. If you are shipping a product that relies on gcc, then for the 10.x = timeframe, you are free to build and use the gcc from the base system, = and the tinderboxes will prevent any non-optional components from being = modified in such a way that they can't build with this gcc. In the 11.x = timeframe, architectures that aren't supported by clang will need an = external toolchain. =20 AMD, Intel, AMD, Oracle, ARM, and MIPS are all actively contributing to = LLVM and Clang, so the only platform that is unlikely to have an LLVM = back end in the 11.0 timeframe is IA64, and if you really care about = IA64 then Intel will happily sell you a compiler that does a much better = job than GCC of targeting this architecture. David --Apple-Mail=_69A682A3-CBD1-4732-B617-BCAE64BAB327 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJSGIVbAAoJEKx65DEEsqId0egQAMvbN7D098fi3SlVoIPiiQFA 28ZZuzTOTFqN/Oa8J91TmpQXBCF08D5S0zVYU1lTCzdvb8YpL++uTCvcaa3C5/19 xsSX0Z67JPq72PTIt3uWAjzDbYWAkZI8KugCQAxhlrI+eYFQ4MvqUPT084+FlzN6 3pRZ00npFz51DSME2/kJoTu50QkdAhACij1bcNcndGRns4Z0HgbNPGuIJnx0/Ix8 3ZuxiCOCrtvWCHQfrJWA51vroY+z6vHKpylX+IvFqyI6XJNI4lIViGD0r1fikkq7 DD33jL3qC7Yc6cJchJfmd8iURWJOztNn1rydukoFjXR86kmja4ekeG9JxIGiQidQ uGE4VPtTltUwv7d1UI+XTEQSLi02hqoVbW6oUHVp30Kw5uGaRKt9H9xtIz+3U+l9 gRiSBd8fxn2yhpqHTsGsQ2p5EYpKP0TOEIeWCmuA51V/dciUEwRG3dMF6goXoM42 yjoeWd9m234YDFRq1HPr/0RzuTMXb8YN3S+2IpBXOL8PRXZk6RyR0P8AncH62Bgs ld4P0Z5DkJ1R0DgnR4AYZAp04rfSWiCmVdvKXp+YFTlNfn484WVWKOUlQZCizCsb TDAVg4cEkV4bwsZguCmgwahyJ5LDxiLBZ3Ouph6dOSYK4TThtNhdYR3pAzIofSLV o+2fKlJOcZeiCK6CmDFt =09Fb -----END PGP SIGNATURE----- --Apple-Mail=_69A682A3-CBD1-4732-B617-BCAE64BAB327-- From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 10:30:26 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4212DB0F; Sat, 24 Aug 2013 10:30:26 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-ve0-x233.google.com (mail-ve0-x233.google.com [IPv6:2607:f8b0:400c:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E384E2675; Sat, 24 Aug 2013 10:30:25 +0000 (UTC) Received: by mail-ve0-f179.google.com with SMTP id c13so1058861vea.24 for ; Sat, 24 Aug 2013 03:30:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NsyY9RKbDWjWGPwI3d2k/coa2u0cbHz79uH+kd0/Hi4=; b=xhon9Zr1VVXsi7ugO7FQXD2mkdE/S+Mgl0JOoijFk/PRHTrotQaDK9kSzNGony0P0O DKRWkLQusiASc1nl55fsbl7E2rgPQr+w72N1Ru/KhBTavYQLCRa+dRzy8FOQdh67XBbY 5fRTPzrls+uNWacL9ilb5g5ZcQik2n/gzkTJEcMiGU6opx0/GL2S1y1RMWY8nzYy3WYu y03BWQ0lmitW9daf+vV6JGWU6RE1SlEWm8T+RyO5ibPI6VgMZcQ7KIbrv9KgwhwAmPVb Yjpo/S0yT0eOhCQpwRveDeI9dkDHBgGbaKdCqwIT0JMIWoYicsuqIotZltvkRS3QV/bo AVVQ== MIME-Version: 1.0 X-Received: by 10.220.199.5 with SMTP id eq5mr3909053vcb.16.1377340224997; Sat, 24 Aug 2013 03:30:24 -0700 (PDT) Received: by 10.220.96.78 with HTTP; Sat, 24 Aug 2013 03:30:24 -0700 (PDT) In-Reply-To: <521745F2.8050607@passap.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> Date: Sat, 24 Aug 2013 06:30:24 -0400 Message-ID: Subject: Re: GCC withdraw From: "Sam Fourman Jr." To: Boris Samorodov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: toolchain@freebsd.org, FreeBSD Current X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 10:30:26 -0000 > If the 150 ports that only work with gcc, all work with a ports > > gcc and do not need the gcc from base, would the following be OK ? > > > > - 9.x gcc default and clang in base; > > - 10.x clang default and gcc in ports; > > Well, we write rules and we brake them. ;-) > > Just say that we know we brake them but it's inevitable because... > And go futher. > I am not a developer, just a user, so I am not versed in all of the issues but I would REALLY like to see gcc moved to ports for 10.x In my opinion this just needs to happen, if ports break, we deal with that on a case by case basis. FreeBSD as a community made the decision to move to clang as a compiler, and moving gcc to ports enforces that decision, I prefer the "rip the band aid off" approach because it brings issues to light faster, and now people have real reasons to fix things. Now, I am aware that other architectures like ARM etc. need gcc in base for basic things like building kernel/world, because clang cant do this yet. Maybe this is over simplifying it a bit but can't we just modify scripts in some way to pull gcc from ports into base, for these platforms at build time? SVN *is* in base now (svnlite) >From an outside look at this, it seems to me that we're holding back the amd64 platform just because the developer activity is a little more sparse than we would prefer on other platforms. Other platforms are important and they are needed, but those platforms are the ones that need patched up, they are the ones that need the band-aids implemented so that gcc still works for them. So I vote, let's not give ourselves the burden of "lugging" dead weight in base for another 5 years. (in 2017 do we still want to be worrying about gcc in base?) So in the name of progress, let's make a comfortable final resting place for gcc in our ports tree and look to clang for our future. Thoughts, Sam Fourman Jr. From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 11:19:31 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 36DE075E; Sat, 24 Aug 2013 11:19:31 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 04F892865; Sat, 24 Aug 2013 11:19:30 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7OBJRgJ009537 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 24 Aug 2013 11:19:29 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: GCC withdraw From: David Chisnall In-Reply-To: Date: Sat, 24 Aug 2013 12:19:22 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> To: "Sam Fourman Jr." X-Mailer: Apple Mail (2.1508) Cc: toolchain@FreeBSD.org, Boris Samorodov , FreeBSD Current X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 11:19:31 -0000 On 24 Aug 2013, at 11:30, "Sam Fourman Jr." wrote: > So I vote, let's not give ourselves the burden of "lugging" dead = weight in > base > for another 5 years. (in 2017 do we still want to be worrying about = gcc in > base?) Perhaps more to the point, in 2017 do we want to be responsible for = maintaining a fork of a 2007 release of gcc and libstdc++? David From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 11:49:54 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6F07EF7; Sat, 24 Aug 2013 11:49:54 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 2E73729D1; Sat, 24 Aug 2013 11:49:54 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VDCNq-000NUP-JB; Sat, 24 Aug 2013 15:51:58 +0400 Date: Sat, 24 Aug 2013 15:51:58 +0400 From: Slawa Olhovchenkov To: "Sam Fourman Jr." Subject: Re: GCC withdraw Message-ID: <20130824115158.GA88999@zxy.spb.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: toolchain@freebsd.org, Boris Samorodov , FreeBSD Current X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 11:49:54 -0000 On Sat, Aug 24, 2013 at 06:30:24AM -0400, Sam Fourman Jr. wrote: > > If the 150 ports that only work with gcc, all work with a ports > > > > gcc and do not need the gcc from base, would the following be OK ? > > > > > > - 9.x gcc default and clang in base; > > > - 10.x clang default and gcc in ports; > > > > Well, we write rules and we brake them. ;-) > > > > Just say that we know we brake them but it's inevitable because... > > And go futher. > > > > I am not a developer, just a user, so I am not versed in all of the > issues but I > would REALLY like to see gcc moved to ports for 10.x > > In my opinion this just needs to happen, if ports break, we deal with that > on a case by case basis. Oh, I remember. mplayer on i386 can't be builded witch clang -- clang don't understand inlined asm. From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 12:10:55 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2CB10B77; Sat, 24 Aug 2013 12:10:55 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EEA712B34; Sat, 24 Aug 2013 12:10:54 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7OCApLv009902 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 24 Aug 2013 12:10:53 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: GCC withdraw From: David Chisnall In-Reply-To: <20130824115158.GA88999@zxy.spb.ru> Date: Sat, 24 Aug 2013 13:10:46 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> <20130824115158.GA88999@zxy.spb.ru> To: Slawa Olhovchenkov X-Mailer: Apple Mail (2.1508) Cc: "Sam Fourman Jr." , toolchain@FreeBSD.org, Boris Samorodov , FreeBSD Current X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 12:10:55 -0000 On 24 Aug 2013, at 12:51, Slawa Olhovchenkov wrote: > Oh, I remember. mplayer on i386 can't be builded witch clang -- clang > don't understand inlined asm. Clang supports inline asm. If there is some specific inline asm syntax = that clang does not recognise, then please will you point me to the = relevant LLVM bug report and I will investigate it. David From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 12:11:18 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0F3BECA1; Sat, 24 Aug 2013 12:11:18 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-vc0-x22d.google.com (mail-vc0-x22d.google.com [IPv6:2607:f8b0:400c:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AF8162B42; Sat, 24 Aug 2013 12:11:17 +0000 (UTC) Received: by mail-vc0-f173.google.com with SMTP id id13so1065239vcb.18 for ; Sat, 24 Aug 2013 05:11:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Dg2Fu5IZVjufd5+00uNB4JxU2vLkC+FMilxbUzmznCo=; b=E3KiCyOV9vma0hqmwxjfrB/qFNUEu65vU+Vk+sJbAWnqVBvdCXNZofpUuXe1gyLdP1 054Ccxzllt5VLaUXSiI7fAg9gstNM2VLW3bOi2VwVRCsMtTszMRxXS2DNHjz2Y7GUbIV kug+6IKDTjS6ACQ6FYgaD45zwPxZ9qaYHWKjN7//XH1HChV0OXJTvEYVH9MNQkYwFAFX lhHtHmfqlX0j5Vcu/9kXaU7YlFSJkTClwtHZVR7vijI/WbpU4c573MP9VPxH1OLXlpqZ 98OKJXDgY10oJXtyIPrp09m45VQ7ooQWugnybmCanexU3rgBL3/M5/3tAECZyl+E7aDB wf4g== MIME-Version: 1.0 X-Received: by 10.58.235.69 with SMTP id uk5mr4294518vec.17.1377346276843; Sat, 24 Aug 2013 05:11:16 -0700 (PDT) Received: by 10.220.96.78 with HTTP; Sat, 24 Aug 2013 05:11:16 -0700 (PDT) In-Reply-To: <20130824115158.GA88999@zxy.spb.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> <20130824115158.GA88999@zxy.spb.ru> Date: Sat, 24 Aug 2013 12:11:16 +0000 Message-ID: Subject: Re: GCC withdraw From: "Sam Fourman Jr." To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: toolchain@freebsd.org, Boris Samorodov , FreeBSD Current X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 12:11:18 -0000 > In my opinion this just needs to happen, if ports break, we deal with that > > on a case by case basis. > > Oh, I remember. mplayer on i386 can't be builded witch clang -- clang > don't understand inlined asm. > > Well, in this case, you would just have the mplayer maintainer configure the port to use gcc for the i386 build of mplayer... problem solved -- Sam Fourman Jr. From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 12:16:00 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7A00DE04; Sat, 24 Aug 2013 12:16:00 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 376252B6C; Sat, 24 Aug 2013 12:16:00 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VDCn7-000NiR-Vd; Sat, 24 Aug 2013 16:18:05 +0400 Date: Sat, 24 Aug 2013 16:18:05 +0400 From: Slawa Olhovchenkov To: "Sam Fourman Jr." Subject: Re: GCC withdraw Message-ID: <20130824121805.GD3796@zxy.spb.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> <20130824115158.GA88999@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: toolchain@freebsd.org, Boris Samorodov , FreeBSD Current X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 12:16:00 -0000 On Sat, Aug 24, 2013 at 12:11:16PM +0000, Sam Fourman Jr. wrote: > > In my opinion this just needs to happen, if ports break, we deal with that > > > > on a case by case basis. > > > > Oh, I remember. mplayer on i386 can't be builded witch clang -- clang > > don't understand inlined asm. > > > > > Well, in this case, you would just have the mplayer maintainer configure the > port to use gcc for the i386 build of mplayer... problem solved Yes, I just edit Makefile. But this is point about ports builded by clang. From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 14:33:38 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7DEA4FC3; Sat, 24 Aug 2013 14:33:38 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4D6492124; Sat, 24 Aug 2013 14:33:37 +0000 (UTC) Received: from jre-mbp.elischer.org (etroy.elischer.org [121.45.226.51]) (authenticated bits=0) by vps1.elischer.org (8.14.6/8.14.6) with ESMTP id r7OEXOvf005390 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 24 Aug 2013 07:33:26 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <5218C42E.1070901@freebsd.org> Date: Sat, 24 Aug 2013 22:33:18 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: David Chisnall Subject: Re: GCC withdraw References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Sam Fourman Jr." , toolchain@FreeBSD.org, Boris Samorodov , FreeBSD Current X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 14:33:38 -0000 On 8/24/13 7:19 PM, David Chisnall wrote: > On 24 Aug 2013, at 11:30, "Sam Fourman Jr." wrote: > >> So I vote, let's not give ourselves the burden of "lugging" dead weight in >> base >> for another 5 years. (in 2017 do we still want to be worrying about gcc in >> base?) > Perhaps more to the point, in 2017 do we want to be responsible for maintaining a fork of a 2007 release of gcc and libstdc++? The same work needs to be done no matter where it is.. there is no saving in moving it, and a lot of hassle.. leave the damned thing alone and be thankful that we have switched to clang by default! don't over-reach your successes. > > David > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 15:40:12 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3E02E3D4; Sat, 24 Aug 2013 15:40:12 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id EF308241A; Sat, 24 Aug 2013 15:40:11 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VDFyj-000P0k-V5; Sat, 24 Aug 2013 19:42:17 +0400 Date: Sat, 24 Aug 2013 19:42:17 +0400 From: Slawa Olhovchenkov To: David Chisnall Subject: Re: GCC withdraw Message-ID: <20130824154217.GE3796@zxy.spb.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> <20130824115158.GA88999@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: "Sam Fourman Jr." , toolchain@FreeBSD.org, Boris Samorodov , FreeBSD Current X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 15:40:12 -0000 On Sat, Aug 24, 2013 at 01:10:46PM +0100, David Chisnall wrote: > On 24 Aug 2013, at 12:51, Slawa Olhovchenkov wrote: > > > Oh, I remember. mplayer on i386 can't be builded witch clang -- clang > > don't understand inlined asm. > > Clang supports inline asm. If there is some specific inline asm > syntax that clang does not recognise, then please will you point me > to the relevant LLVM bug report and I will investigate it. Sorry, I don't know about clang/llvm bug reports, I just try to build mplayer with Win32 codecs support on FreeBSD-10/i386. And currenly (in rev r315041) building by clang disabled in ports tree. PS: Also, if FreeBSD ship clang why ship not full set of clang? For example, when I try to build llvm-lua not found sets of files: LLVMCompiler.cpp:25:30: error: llvm/LLVMContext.h: No such file or directory LLVMCompiler.cpp:26:31: error: llvm/DerivedTypes.h: No such file or directory LLVMCompiler.cpp:27:50: error: llvm/ExecutionEngine/ExecutionEngine.h: No such file or directory LLVMCompiler.cpp:28:25: error: llvm/Module.h: No such file or directory LLVMCompiler.cpp:29:30: error: llvm/PassManager.h: No such file or directory LLVMCompiler.cpp:30:36: error: llvm/Analysis/Verifier.h: No such file or directory LLVMCompiler.cpp:31:36: error: llvm/Target/TargetData.h: No such file or directory LLVMCompiler.cpp:32:39: error: llvm/Target/TargetMachine.h: No such file or directory LLVMCompiler.cpp:33:40: error: llvm/Target/TargetOptions.h: No such file or directory LLVMCompiler.cpp:34:36: error: llvm/Transforms/Scalar.h: No such file or directory LLVMCompiler.cpp:35:33: error: llvm/Transforms/IPO.h: No such file or directory LLVMCompiler.cpp:36:43: error: llvm/Transforms/Utils/Cloning.h: No such file or directory LLVMCompiler.cpp:37:36: error: llvm/Support/IRBuilder.h: No such file or directory LLVMCompiler.cpp:38:32: error: llvm/Support/Timer.h: No such file or directory LLVMCompiler.cpp:39:38: error: llvm/Support/CommandLine.h: No such file or directory From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 15:42:11 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EB74C661 for ; Sat, 24 Aug 2013 15:42:11 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B669A2462 for ; Sat, 24 Aug 2013 15:42:11 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id aq17so2660103iec.13 for ; Sat, 24 Aug 2013 08:42:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=cECSnYUFag5Y5kHUjMRJNA+BQ8xOAnDFKMSgkETnEIo=; b=iiryJ9SUj0koH8AMncrNdnAXY0i3Joz3QWYbwvdiFDkIXBPCT79chdbnFyYBatcUqE xi6CWf+qupKhax/sfc4U9aD9BMQRUFRGsMoY7cBzjV/bSEcXK51to+jTYDdxYEJWSJCW k7k3rbF53V8NNqTqYQGgxQ79tejPPKxL6MFBkzSYqYv7UkMwqqKbIFocUz6iocEXAd5o RG2AAg+KYqzNb2WbE0iCQjVp8HKH4h6JBroJC06/LgN6gvGYvNBZQVpafGgm/mjLxIYP +VH54hHsfEWTx85UwiZv3v+UgupJ7u+5OTt7pqN49OwT036jk02pOpLTphUWqizKPPM3 XCsg== X-Gm-Message-State: ALoCoQl7kGqp9XJ5bfmmVQLjjw3B2ltwIJayAVebbu0XmkAvDUOsE5lmZu2vq3AjRu5qbbNLAKEf X-Received: by 10.50.119.42 with SMTP id kr10mr1695285igb.20.1377358925608; Sat, 24 Aug 2013 08:42:05 -0700 (PDT) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id p10sm4925151igx.4.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 24 Aug 2013 08:42:04 -0700 (PDT) Sender: Warner Losh Subject: Re: patch to add AES intrinsics to gcc Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <1380949A-254A-4222-BEDE-0C23E16E4F67@freebsd.org> Date: Sat, 24 Aug 2013 09:42:02 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <8C31A000-6806-4291-98A4-E8291E637BD2@bsdimp.com> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <5217DBAB.5030607@freebsd.org> <86032E72-A569-4946-B4F8-26F687067B31@bsdimp.com> <1380949A-254A-4222-BEDE-0C23E16E4F67@freebsd.org> To: David Chisnall X-Mailer: Apple Mail (2.1085) Cc: toolchain@freebsd.org, John-Mark Gurney , Alfred Perlstein , "re@FreeBSD.org Engineering Team" , current@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 15:42:12 -0000 On Aug 24, 2013, at 4:05 AM, David Chisnall wrote: > On 23 Aug 2013, at 23:37, Warner Losh wrote: >=20 >> I'd dispute the 'and surely it seems like it does' part of this. Non = x86 architectures will continue to use gcc because clang just isn't = ready at this time for them. Some are very close (arm), some are close = (powerpc64, mips*), some are no where near ready, or will never be ready = (sparc64, ia64). There's no coherent, documented plan for these absent = gcc at the moment. There are lots of pieces there, and those pieces will = form the basis of the solution (+handbook updates) for the removal of = gcc in 11, but we just aren't there yet. >=20 > The plan, which has been discussed on mailing lists, on IRC, and at = DevSummits is for tier 2 ports to depend on an external toolchain. For = those vendors that are not prevented from using GPLv3 compilers, this = means that they will be able to take advantage of, for example, the = significant improvements to the MIPS and PowerPC back ends that gcc has = had over the last 6 years. For everyone else, it will mean installing a = compiler from ports. That's the plan for FreeBSD 11, yes. For FreeBSD 10, gcc remains in the = tree. > For now, tier 2 architectures will continue to build a toolchain from = the src tree and use that. By 11.0, gcc will be gone from the base = system and they will be required to use something external if they are = not supported by clang. Brooks has been working hard on making this = easy, and it is generally an improvement for cross-building embedded = systems as the cross-compile toolchain is no longer rebuilt every time = you change a file in the kernel, resulting in faster builds. It is also = easier to use toolchains provided by chip vendors, which is something = that MIPS and ARM vendors have been asking for for a very long time. =20 Yes. Many of the building blocks are in place, but they haven't been = stitched together entirely yet. The 11 time frame is plenty of time to = tie up the loose ends and rough edges that are there, as well as to = ensure you can cross build a system, then do a native build on that = system with external toolchains... > For x86 and ARMv6/7, Clang has been the default compiler for a long = time and gcc has been increasingly problematic (for example, our gcc = does not support ARM EABI, which will be the default in 10.0 for ARMv6 = and later, so if you want to build for a modern ARM chip then you need = either clang or a more recent gcc than we ship). Claiming that this is = something done at the expense of non-x86 architectures is highly = misleading, as improving ARM support is one of the driving factors = behind the switch. I'm sorry, but that's not quite right. Our gcc *DOES* support arm EABI = with soft float. In fact, that's how we're using it now and how we're = using clang now as well. clang support for ARM is still shaky, even in = -current. EABI with hard float hasn't been done, and will require a = newer gcc and/or clang, but we're not entirely there yet. The fallback = for weird bugs is still "recompile with the in-tree gcc" and often that = has fixed issues that people hit either with clang, or with assumptions = about generated code that weren't quite true with clang and needed to be = fixed in our kernel. But *ALL* the other non-x86 architectures are significantly worse with = clang. ARM is marginally the same, but we're still some issues we're = fighting through with ports and such. I think I was clear about which = ones were affected, and how though in my note. > If you are shipping a product that relies on gcc, then for the 10.x = timeframe, you are free to build and use the gcc from the base system, = and the tinderboxes will prevent any non-optional components from being = modified in such a way that they can't build with this gcc. In the 11.x = timeframe, architectures that aren't supported by clang will need an = external toolchain. =20 Yup. And the external toolchain support will need to be well documented = and we need a cross building/installing external toolchain story that's = better. It works well enough to generate a system now, but not quite = well enough to generate a self-hosting system (which is required for the = ports cross-build-on-qemu solution). > AMD, Intel, AMD, Oracle, ARM, and MIPS are all actively contributing = to LLVM and Clang, so the only platform that is unlikely to have an LLVM = back end in the 11.0 timeframe is IA64, and if you really care about = IA64 then Intel will happily sell you a compiler that does a much better = job than GCC of targeting this architecture. Yes. I'm totally on board with that for the 11 time frame. 32-bit = powerpc had issues, and isn't in your list. Warner= From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 15:43:56 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D46187B6 for ; Sat, 24 Aug 2013 15:43:56 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9FF952484 for ; Sat, 24 Aug 2013 15:43:56 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id aq17so2661648iec.13 for ; Sat, 24 Aug 2013 08:43:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=A+Yh7oD40GRU8V05/2b62MuUYN81IFctaL+FokqHoCE=; b=ku4au9ZnyzhpYm+Rzh3B+RK1QOyBDCf/zLjZcaiy2nH4OGD3zW1oMlgSVdGoVhfxJq lGxZUZe83YGOesvBxOIrzoin5FF0f1dGzz3ht28hVNwOyimh1JwLUx1mWSHgNIsQrFIM Jo7KPg0qGgKbUhxlnvF+rwi+mWzfg9x9X/Fc0bq6PMU5+/59KHoy+t9kJA2rNmIrnTTd vCrS6+XAwK+q44m4uCouPdOh53vJp38PBB4qkmmZpJ0EANIKnFMk6CChXuRVOFnFeP9V QZ8D1NVdMYJMUyqVRjzxBGKzVjRZMdsKJDmLQ7ND85wlaly26Bi83/JCpLmLa8V8pxfA EwqA== X-Gm-Message-State: ALoCoQl05iJhmhD1bqanfKMadxyTfXZK7k5VXAxRqzbxXb5X90duw/McGDaDG6xIYbQQ9Tt7amwO X-Received: by 10.50.39.51 with SMTP id m19mr1594986igk.51.1377359035948; Sat, 24 Aug 2013 08:43:55 -0700 (PDT) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id yt10sm4901119igb.9.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 24 Aug 2013 08:43:55 -0700 (PDT) Sender: Warner Losh Subject: Re: GCC withdraw Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Sat, 24 Aug 2013 09:43:53 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> <20130824115158.GA88999@zxy.spb.ru> To: "Sam Fourman Jr." X-Mailer: Apple Mail (2.1085) Cc: toolchain@freebsd.org, Boris Samorodov , FreeBSD Current , Slawa Olhovchenkov X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 15:43:56 -0000 On Aug 24, 2013, at 6:11 AM, Sam Fourman Jr. wrote: >> In my opinion this just needs to happen, if ports break, we deal with = that >=20 >>> on a case by case basis. >>=20 >> Oh, I remember. mplayer on i386 can't be builded witch clang -- clang >> don't understand inlined asm. >>=20 >>=20 > Well, in this case, you would just have the mplayer maintainer = configure the > port to use gcc for the i386 build of mplayer... problem solved The problem is that there's a lot of cases in ports where this work = needs to be done. That work is ongoing, but isn't done yet. The ports = people have indicated that in the 10 time frame may be a bit = optimistic... Warner From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 16:33:42 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CE45DB39; Sat, 24 Aug 2013 16:33:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B7DD0272E; Sat, 24 Aug 2013 16:33:41 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id l12so1405658wiv.1 for ; Sat, 24 Aug 2013 09:33:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=8wHn1YcEO1JJANmqLfD92mzDM2MzUcim79TS7Y95bSI=; b=Q9BwV2JjDUz6KIzIl0gl2JlBwWAfEwtr/S4iNgp2YbtIqk6DEca71xsZKyVblbLQ0f +8lQOvtRNyqS9roKytHAXWSR2KEBEo8YRZgvrXbctO1BpLcyuoCmCrOjtnGbaahLDa8t g4szdoVYLSZvOVEwmpzop6nFUFNMYLYqBXuSzejRKss4U2XBFrZuIC+H5BupipJdiC1Q J1oA+niDLWErYp4i5n1WuwKai/nHi9oXxfr6R5RgHYRHjQWjizFHCcrY4UVjPqLDLz8H KiVMPdF3XG5AQKCEedcBwqRXNCz00bqRKKzTciVta4PrAVvoBlbWx60KvSQ/kcSTctzx xyOw== MIME-Version: 1.0 X-Received: by 10.180.36.133 with SMTP id q5mr2006182wij.0.1377362020059; Sat, 24 Aug 2013 09:33:40 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.116.136 with HTTP; Sat, 24 Aug 2013 09:33:39 -0700 (PDT) In-Reply-To: <8C31A000-6806-4291-98A4-E8291E637BD2@bsdimp.com> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <5217DBAB.5030607@freebsd.org> <86032E72-A569-4946-B4F8-26F687067B31@bsdimp.com> <1380949A-254A-4222-BEDE-0C23E16E4F67@freebsd.org> <8C31A000-6806-4291-98A4-E8291E637BD2@bsdimp.com> Date: Sat, 24 Aug 2013 09:33:39 -0700 X-Google-Sender-Auth: LmgMJa5W5PlabcqRj1Esxu7DZpg Message-ID: Subject: Re: patch to add AES intrinsics to gcc From: Adrian Chadd To: Warner Losh Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "re@FreeBSD.org Engineering Team" , "current@freebsd.org" , John-Mark Gurney , Alfred Perlstein , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 16:33:42 -0000 You know, I could be a total jerk and say: "If you push gcc out to a port, and you have the 'external compiler' toolchain support working correctly enough to build with this, why don't we just push clang out to a port, and be done with it?" ... just saying. -adrian From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 16:40:02 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4C78490; Sat, 24 Aug 2013 16:40:02 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 31836279A; Sat, 24 Aug 2013 16:40:01 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-67-180-208-218.hsd1.ca.comcast.net [67.180.208.218]) by elvis.mu.org (Postfix) with ESMTPSA id AFA921A3DA7; Sat, 24 Aug 2013 09:40:01 -0700 (PDT) Message-ID: <5218E1E1.1040809@freebsd.org> Date: Sat, 24 Aug 2013 09:40:01 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <5217DBAB.5030607@freebsd.org> <86032E72-A569-4946-B4F8-26F687067B31@bsdimp.com> <1380949A-254A-4222-BEDE-0C23E16E4F67@freebsd.org> <8C31A000-6806-4291-98A4-E8291E637BD2@bsdimp.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "re@FreeBSD.org Engineering Team" , "current@freebsd.org" , John-Mark Gurney , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 16:40:02 -0000 On 8/24/13 9:33 AM, Adrian Chadd wrote: > You know, I could be a total jerk and say: > > "If you push gcc out to a port, and you have the 'external compiler' > toolchain support working correctly enough to build with this, why don't we > just push clang out to a port, and be done with it?" > > ... just saying. > > > > -adrian > Are you calling me a total jerk? :) I'm fine with that because I agree. -Alfred From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 19:58:38 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6CC07A1F; Sat, 24 Aug 2013 19:58:38 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 251AB202F; Sat, 24 Aug 2013 19:58:37 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VDK0o-0000r2-6e; Sun, 25 Aug 2013 00:00:42 +0400 Date: Sun, 25 Aug 2013 00:00:42 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: patch to add AES intrinsics to gcc Message-ID: <20130824200042.GF3796@zxy.spb.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <20130823114635.GB64913@zxy.spb.ru> <20130823210513.GA3796@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130823210513.GA3796@zxy.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: "re@FreeBSD.org Engineering Team" , "current@freebsd.org" , John-Mark Gurney , toolchain@freebsd.org, Julian Elischer X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 19:58:38 -0000 On Sat, Aug 24, 2013 at 01:05:13AM +0400, Slawa Olhovchenkov wrote: > On Fri, Aug 23, 2013 at 06:54:44AM -0700, Adrian Chadd wrote: > > > Hi! > > > > If firewire code doesn't build on clang correctly, have you filed a bug so > > it gets looked at before 10.0 is released? that's pretty broken > > code/behaviour. > > How I can do it correctly? > Currently in src.conf: > > WITHOUT_CLANG=yes > WITHOUT_CLANG_IS_CC=yes > > Need recompile world? > System build from sources Jun 8. clang -- Jan 9. I build world w/o this options. After this I build kernel and install it. Reboot. acpiconf -s 3. power button. I got NMI. Sorry, dump don't allowed -- dump device don't ready at this moment. This is screenphoto http://zxy.spb.ru/13080005.jpg Kernel builded by GCC succeseful resuming (w/o NMI). Is it sufficient information for open PR? From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 21:04:01 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D488CCB2; Sat, 24 Aug 2013 21:04:01 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-vb0-x232.google.com (mail-vb0-x232.google.com [IPv6:2607:f8b0:400c:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 322282332; Sat, 24 Aug 2013 21:04:01 +0000 (UTC) Received: by mail-vb0-f50.google.com with SMTP id x14so1289456vbb.9 for ; Sat, 24 Aug 2013 14:04:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zjMZc18z4d9IrtLa0mOydDJzOCz7pW7Ikxyy4Q0c35U=; b=nmJc0MdkTyLpWa86U+RVidB6ivtbdbeQvJlw6YY4nHjqrN9BRoNTz+c3qQOlUPWAyN w2PIe/JsiKXjltbR84Vz8lP3/Cs8DN5i0MJRhHca9V3TuXQfxnVfDngmo/ngdMpJi4ie +KpuXtEF6fi4HsPy9ixJfYNPmuuMMdd9PWoU80gRtJ9rZLDo8Wh1jN8r+FyvyYDUGZVx HkoeT4ONAizJR1MZtsAY6lvozEhkZ5g7oM94F1gYGP71ICHPJDjl/U041F8tN6gz910/ Le2/G0zSM2+/B2BhyV0BEQ1B/1cUl8u+B9dJtlOiJZooZ8SgwxQIRQHX4eRueirt/bFT zvCQ== MIME-Version: 1.0 X-Received: by 10.221.51.206 with SMTP id vj14mr6251358vcb.17.1377378240173; Sat, 24 Aug 2013 14:04:00 -0700 (PDT) Received: by 10.220.96.78 with HTTP; Sat, 24 Aug 2013 14:04:00 -0700 (PDT) In-Reply-To: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <5217DBAB.5030607@freebsd.org> <86032E72-A569-4946-B4F8-26F687067B31@bsdimp.com> <1380949A-254A-4222-BEDE-0C23E16E4F67@freebsd.org> <8C31A000-6806-4291-98A4-E8291E637BD2@bsdimp.com> Date: Sat, 24 Aug 2013 17:04:00 -0400 Message-ID: Subject: Re: patch to add AES intrinsics to gcc From: "Sam Fourman Jr." To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "re@FreeBSD.org Engineering Team" , "current@freebsd.org" , John-Mark Gurney , Alfred Perlstein , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 21:04:01 -0000 On Sat, Aug 24, 2013 at 12:33 PM, Adrian Chadd wrote: > You know, I could be a total jerk and say: > > "If you push gcc out to a port, and you have the 'external compiler' > toolchain support working correctly enough to build with this, why don't we > just push clang out to a port, and be done with it?" > > ... just saying. +1 GREAT idea!!! that is a better plan for 11.x -- Sam Fourman Jr. From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 21:17:50 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B8E14A64 for ; Sat, 24 Aug 2013 21:17:50 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 809502414 for ; Sat, 24 Aug 2013 21:17:50 +0000 (UTC) Received: by mail-ie0-f175.google.com with SMTP id u16so2747961iet.6 for ; Sat, 24 Aug 2013 14:17:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=1ypc3mi7HhJawtbcGrUIFOCSjoc/RSRyDVngXTyh7oQ=; b=ivvXp71JSYOZe6p0aBMsHD9M0BKpIsQw4wLPTIWXVLptrpUQUKK00UzqTxJ0CxzSfJ bT/n7heV8qIC7SddfKy4/DQW+O9D9HP8P0dCNAwIh9egWm0qT4jF5JQXuh4gom4XXc5J ezqDYA8w30oRoGUi3pHuDZW+KDzAcTrAIHHUkvuql3pzjuiERlX3ycqqAg4Mn6QvgwrD AWcgjhj4ZpUIIFAkvfVcHZ/JSRUk66XQ/8H9p9k/T0JnH5+niglAy/mcqtPj4M3Zs3Fy p6itBpB39izo7sgp6FkgS4Oa2aeAmGGuxn4CkvUfdvSC7Bxh+08tom8Jbm0WpsdNFaEo bVZw== X-Gm-Message-State: ALoCoQlcIujKwUoXedtjQqDzTfNxSevfcsNcajMn4UKPqy0jA4/fP7aG1wDjwPiYDf8DMp0/qn0A X-Received: by 10.42.147.198 with SMTP id o6mr3506992icv.13.1377379064152; Sat, 24 Aug 2013 14:17:44 -0700 (PDT) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id f5sm6823755igc.4.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 24 Aug 2013 14:17:43 -0700 (PDT) Sender: Warner Losh Subject: Re: patch to add AES intrinsics to gcc Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Sat, 24 Aug 2013 15:17:41 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <5217DBAB.5030607@freebsd.org> <86032E72-A569-4946-B4F8-26F687067B31@bsdimp.com> <1380949A-254A-4222-BEDE-0C23E16E4F67@freebsd.org> <8C31A000-6806-4291-98A4-E8291E637BD2@bsdimp.com> To: "Sam Fourman Jr." X-Mailer: Apple Mail (2.1085) Cc: Adrian Chadd , "re@FreeBSD.org Engineering Team" , "current@freebsd.org" , John-Mark Gurney , Alfred Perlstein , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 21:17:50 -0000 On Aug 24, 2013, at 3:04 PM, Sam Fourman Jr. wrote: >=20 >=20 >=20 > On Sat, Aug 24, 2013 at 12:33 PM, Adrian Chadd = wrote: > You know, I could be a total jerk and say: >=20 > "If you push gcc out to a port, and you have the 'external compiler' > toolchain support working correctly enough to build with this, why = don't we > just push clang out to a port, and be done with it?" >=20 > ... just saying. >=20 > +1 >=20 > GREAT idea!!! that is a better plan for 11.x=20 This is a stupid idea. It kills the tightly integrated nature of = FreeBSD. I'd say it is far too radical a departure and opens up a huge = can of "which version of what compiler" nightmare that we've largely = dodged to date because we had one (or maybe two) compilers in the base = system. Warner From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 22:40:00 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0504F467; Sat, 24 Aug 2013 22:40:00 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id B27C8282E; Sat, 24 Aug 2013 22:39:59 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VDMWy-0001qv-Tm; Sun, 25 Aug 2013 02:42:04 +0400 Date: Sun, 25 Aug 2013 02:42:04 +0400 From: Slawa Olhovchenkov To: David Chisnall Subject: Re: GCC withdraw Message-ID: <20130824224204.GH3796@zxy.spb.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> <20130824115158.GA88999@zxy.spb.ru> <20130824154217.GE3796@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130824154217.GE3796@zxy.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: "Sam Fourman Jr." , toolchain@FreeBSD.org, Boris Samorodov , FreeBSD Current X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 22:40:00 -0000 On Sat, Aug 24, 2013 at 07:42:17PM +0400, Slawa Olhovchenkov wrote: > On Sat, Aug 24, 2013 at 01:10:46PM +0100, David Chisnall wrote: > > > On 24 Aug 2013, at 12:51, Slawa Olhovchenkov wrote: > > > > > Oh, I remember. mplayer on i386 can't be builded witch clang -- clang > > > don't understand inlined asm. > > > > Clang supports inline asm. If there is some specific inline asm > > syntax that clang does not recognise, then please will you point me > > to the relevant LLVM bug report and I will investigate it. > > Sorry, I don't know about clang/llvm bug reports, I just try to build > mplayer with Win32 codecs support on FreeBSD-10/i386. > > And currenly (in rev r315041) building by clang disabled in ports tree. And i found PR about clang and mplayer: ports/176272 This PR contains log with build error log. From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 22:44:47 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BC3726E3; Sat, 24 Aug 2013 22:44:47 +0000 (UTC) (envelope-from theraven@freebsd.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6BC9D2885; Sat, 24 Aug 2013 22:44:46 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7OMiiAK014904 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 24 Aug 2013 22:44:45 GMT (envelope-from theraven@freebsd.org) Content-Type: multipart/signed; boundary="Apple-Mail=_E4254B5D-2240-4465-9F57-E543CF9F9925"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: GCC withdraw From: David Chisnall In-Reply-To: <20130824224204.GH3796@zxy.spb.ru> Date: Sat, 24 Aug 2013 23:44:38 +0100 Message-Id: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> <20130824115158.GA88999@zxy.spb.ru> <20130824154217.GE3796@zxy.spb.ru> <20130824224204.GH3796@zxy.spb.ru> To: Slawa Olhovchenkov X-Mailer: Apple Mail (2.1508) Cc: "Sam Fourman Jr." , toolchain@freebsd.org, Boris Samorodov , FreeBSD Current X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 22:44:47 -0000 --Apple-Mail=_E4254B5D-2240-4465-9F57-E543CF9F9925 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 24 Aug 2013, at 23:42, Slawa Olhovchenkov wrote: > And i found PR about clang and mplayer: ports/176272 > This PR contains log with build error log. Please file clang bugs at http://llvm.org/bugs/ David --Apple-Mail=_E4254B5D-2240-4465-9F57-E543CF9F9925 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJSGTdWAAoJEKx65DEEsqIdDXkP/1BA+hphQrLoKR++oKzkOJ9o tB7t/r8cUH/yUxQOBglABuhoj+RG+pCgHaAMdcYzEj8QU7cQmBDJ5+Vuv4vkoOzV Wfa0yWM+bk92LEbeyX/9WffYT0zaLQF1m3PVpONHC7RA7+K5fsELRLT26TiBthIk BJZa84H4KyQEYtHnjp9J6l94kJmogCHTz6Z9F2RO66M8C4XEy2F7ootWJSQOFNTL kywjFojOr7S1/GbOC1Eo713UYkAtLCY5dGQyX9DyrPllALXwXWDIVqNaQpePqiLJ awPAc2LCm/srIkI6bWlG6QB8VoXZZS3Mm12d1sU5P66ecjekgFEDjsPRtFaIqzd0 qGVqmmqXbCZxAujDA+5Uy/UGGZOUNPLx4/ZJ+bOfF1uzeGp2Env/RyxoiRPrRKic Mbb3M530JtbZySKhzM3QB2w5ACShOBqaOZ6KN2Yt9NdnjgTUbpoFDwu5Z1N/Nejp ZSvlDRcMJT3bfDPvcq3bHT8Srlvx7Fou9487vtHCxEi8l18lblcRzRq9SAULRqWw qxzkcQtSXGY6OkY4ePUXdJsvJ1PhrfWMMvFRW3f/oj0RnycjDhwl23rUwbCVdzlX 6WrEIjyVa5DXF7oDS7iBFR0KWTXtId0zQbcmmV40lRxMGBEmhIdxLQJL88vi70hP evNNWCG+3eFyfMGfbPmD =mn45 -----END PGP SIGNATURE----- --Apple-Mail=_E4254B5D-2240-4465-9F57-E543CF9F9925-- From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 23:06:16 2013 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 60126C8E; Sat, 24 Aug 2013 23:06:16 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3B0182999; Sat, 24 Aug 2013 23:06:16 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id r7ON6FqH055902; Sat, 24 Aug 2013 16:06:15 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id r7ON6F2w055901; Sat, 24 Aug 2013 16:06:15 -0700 (PDT) (envelope-from sgk) Date: Sat, 24 Aug 2013 16:06:15 -0700 From: Steve Kargl To: David Chisnall Subject: Re: GCC withdraw Message-ID: <20130824230615.GA55855@troutmask.apl.washington.edu> References: <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> <20130824115158.GA88999@zxy.spb.ru> <20130824154217.GE3796@zxy.spb.ru> <20130824224204.GH3796@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "Sam Fourman Jr." , toolchain@freebsd.org, Boris Samorodov , FreeBSD Current , Slawa Olhovchenkov X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 23:06:16 -0000 On Sat, Aug 24, 2013 at 11:44:38PM +0100, David Chisnall wrote: > On 24 Aug 2013, at 23:42, Slawa Olhovchenkov wrote: > > > And i found PR about clang and mplayer: ports/176272 > > This PR contains log with build error log. > > Please file clang bugs at http://llvm.org/bugs/ > As if this is going to help. http://llvm.org/bugs/show_bug.cgi?id=8532 2 years, 9 month and counting. -- Steve