From owner-freebsd-toolchain@FreeBSD.ORG Sun Sep 1 01:53:56 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 39E4AE62; Sun, 1 Sep 2013 01:53:56 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) by mx1.freebsd.org (Postfix) with ESMTP id ABBC72EF5; Sun, 1 Sep 2013 01:53:55 +0000 (UTC) X-AuditID: 12074422-b7ef78e000000935-57-52229e2d5e87 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 28.EA.02357.D2E92225; Sat, 31 Aug 2013 21:53:49 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id r811rmoh015198; Sat, 31 Aug 2013 21:53:48 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r811rk2P013951 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 31 Aug 2013 21:53:47 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r811rj3R001548; Sat, 31 Aug 2013 21:53:45 -0400 (EDT) Date: Sat, 31 Aug 2013 21:53:45 -0400 (EDT) From: Benjamin Kaduk To: David Chisnall Subject: Re: GCC withdraw In-Reply-To: <98D31DD3-8A1D-46ED-9BF6-9EBE39640860@freebsd.org> Message-ID: References: <20130822200902.GG94127@funkthat.com> <201308291344.25562.jhb@freebsd.org> <201308301041.18874.jhb@freebsd.org> <20130831073330.GC36239@funkthat.com> <98D31DD3-8A1D-46ED-9BF6-9EBE39640860@freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLIsWRmVeSWpSXmKPExsUixCmqras7TynI4P81dosJV34wWSy+/4jZ YsfO62wOzB4zPs1nCWCM4rJJSc3JLEst0rdL4Mp4svUBY8F9nordf5IbGP9wdjFyckgImEhM P/mYFcIWk7hwbz1bFyMXh5DAPkaJOWfuQDkbGSW2/vrGDuEcYpJ41rSIFcJpYJS4/OkTWD+L gLZE0/tWNhCbTUBFYuabjWC2iICmxKTLexhBbGYBB4kPfzqZuhg5OIQFJCV2Ha0DCXMK2Ev8 7j7EAmLzCjhKvP/wEWp+J5PEg0WLwRKiAjoSq/dPgSoSlDg58wkLxExLiXN/rrNNYBSchSQ1 C0lqASPTKkbZlNwq3dzEzJzi1GTd4uTEvLzUIl1TvdzMEr3UlNJNjKBQZXdR2sH486DSIUYB DkYlHt6ASKUgIdbEsuLK3EOMkhxMSqK8GycChfiS8lMqMxKLM+KLSnNSiw8xSnAwK4nwMjQB 5XhTEiurUovyYVLSHCxK4rzPnp4NFBJITyxJzU5NLUgtgsnKcHAoSfAGzgVqFCxKTU+tSMvM KUFIM3FwggznARpuBlLDW1yQmFucmQ6RP8WoKCXOawySEABJZJTmwfXCUskrRnGgV4R5ZUGq eIBpCK77FdBgJqDB1yYqggwuSURISTUwZh43SLZYuN7Z5QlDxc31zvNdXJdpeUeE301ZYKmz 7+g17RXfCy9eOF99nW3ahjMFPVJM/bsnXtqoF70qL/QCq8s9kxKJqvjZ2v4/pvLkPmF69rRu jp/hF+Pgv6aWvsKTlasSFn+vuKmqGz/Vdq5oQajR5d7Aun6L9mfnZj869bZEfX3FUY97SizF GYmGWsxFxYkAQYHGrQADAAA= 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: Sun, 01 Sep 2013 01:53:56 -0000 Sorry for adding to the long thread. On Sat, 31 Aug 2013, David Chisnall wrote: > However, we want to be able to make it unsupported at some point in the > 10.x series when there is a polished alternative for every supported > architecture (either when they've moved to clang or when the XCC stuff I am worried about the definition of "polished". I held my tongue in Ottawa in 2011 when Kirk wanted to turn SU+J on by default, since I figured he knew what was going on much better than I did. Then, we discovered the bad interactions between SU+J and snapshots. If memory serves, things like sparc64 and mips64 support for clang/llvm and XCC suppor are being described as only "a few man-months work away". But that seems to be just to get something which is working ... I fear that to get it truly "polished" will be another 2-3 years on top of those man-months. If we are in agreement about what "polished" means, then by all means announce with 10.0 that gcc's days are numbered and drop it at the appropriate 10.x. I just don't want us to discover terrible bugs a few months after we make a switch, due to being wrong about "polished". -Ben > is fully documented in the handbook and tested in a large variety of > configurations and once our forked binutils and is available as a > package and we have cross-gcc that uses it). If this doesn't happen by > the time 10.x is EOL'd then I'll be sad, but we still have the fall-back > position of gcc in base for the entire 10.x. If it does happen, then we > can start more aggressively phasing out gcc in the base system. From owner-freebsd-toolchain@FreeBSD.ORG Sun Sep 1 07:58:51 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 B9D265B6; Sun, 1 Sep 2013 07:58:51 +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 6B9672C63; Sun, 1 Sep 2013 07:58:50 +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 r817wgLI027898 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 1 Sep 2013 07:58:43 GMT (envelope-from theraven@freebsd.org) Content-Type: multipart/signed; boundary="Apple-Mail=_44BBE6AB-A070-4794-A716-1A9712C2128B"; 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: Date: Sun, 1 Sep 2013 08:58:36 +0100 Message-Id: <1DB38CEA-6821-4206-8F5A-24EDF1483223@freebsd.org> References: <20130822200902.GG94127@funkthat.com> <201308291344.25562.jhb@freebsd.org> <201308301041.18874.jhb@freebsd.org> <20130831073330.GC36239@funkthat.com> <98D31DD3-8A1D-46ED-9BF6-9EBE39640860@freebsd.org> To: Benjamin Kaduk X-Mailer: Apple Mail (2.1508) 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: Sun, 01 Sep 2013 07:58:51 -0000 --Apple-Mail=_44BBE6AB-A070-4794-A716-1A9712C2128B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 1 Sep 2013, at 02:53, Benjamin Kaduk wrote: > I am worried about the definition of "polished". I held my tongue in = Ottawa in 2011 when Kirk wanted to turn SU+J on by default, since I = figured he knew what was going on much better than I did. Then, we = discovered the bad interactions between SU+J and snapshots. If memory = serves, things like sparc64 and mips64 support for clang/llvm and XCC = suppor are being described as only "a few man-months work away". But = that seems to be just to get something which is working ... I fear that = to get it truly "polished" will be another 2-3 years on top of those = man-months. If we are in agreement about what "polished" means, then by = all means announce with 10.0 that gcc's days are numbered and drop it at = the appropriate 10.x. I just don't want us to discover terrible bugs a = few months after we make a switch, due to being wrong about "polished". We are using XCC to build FreeBSD today, on x86 with experimental tools = and on MIPS with the compiler in base. It works, but it could do with = better documentation. That's what I mean by polishing: making sure that = it doesn't just work, it works and is easy to use. Part of this will = involve ensuring that we have packages for cross compilers for various = platforms so that it's really easy to just install a package with the = cross toolchain you want and point your already-installed source tree at = it to get a cross-build environment. =20 Many of us have been running clang-is-cc for a long time and we're now = seeing more port build failures on 10-with-gcc than 10-without-gcc. = That's what I mean by polished. The SPARC back end in LLVM is marked as experimental. Looking over the = code, it's actually in a better state than I thought it would be. Some = people seem to be working on it. It's not something I would count on = getting to a useable state though. If SPARC is to remain a supported = architecture, then we'll probably be using an external toolchain for it, = unless someone wants to spend a couple of months chasing bugs in the = LLVM SPARC back end. Oracle seems to be being quite effective at = killing SPARC64 as an architecture for running anything other than = Oracle appliances, but SPARC32 is still quite popular in aerospace so it = may still be an interesting platform in a few years. David --Apple-Mail=_44BBE6AB-A070-4794-A716-1A9712C2128B 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 iQIcBAEBAgAGBQJSIvOtAAoJEKx65DEEsqIduRQP/AxMrYQDz83DCcd41PHY7+dx GpkOpbW9GKbMr6GM5WbXi8wdUc0aYsl1GZ9wKjvf2wKia+LgHYgSxHehv4/FArTQ zy+Ix//m+bdSw+8PLSZQm7Rh9PAooNhNDF1YHKMrufXq/uZ8L7iL/LUNqV4A+gsR jDlAvCyNIut1M6ZWbjHrRexGbWgVO5Bw1Gd/eYWEIaygJt6D9acN8EbRfBJHWDxe ov59JZOAg6E7oLnWxVgt88WFv3XobuSbLXjOwCiCRSDvJT5TnDrgQ/I+SBR5G2tp U05pXb98apvqid8z9w3GY1WyB6j5HhKKkqr2dfHx5XFzOgCXvO6k63KFrxiB09ZF CJv7cv1CgM/VHb6RmpfCOHsepmePzh1d+RQnDd+YmNfWOP7aKmGN1Dskx1pqPVVH VKg1Ko5XvDAj92ncRwzfrgkVA4wdJMnlLDmOF34SNQ9bs0DAzuplzmVq0sZ2nCdb hMMlUo82VrENFjcRUYar2LZo56p1Dj6fFG8StHjdMarxLxZ08ASFvOeIjgTg6kPN ZYSb5N6nt1taklMN49XIG4NphWj7a3W3uOgF/eML/NNHAcrYVmoZoDSayA2nkUU8 oWFa3DBffDuPi8fiLaMgww18BkjYFpQC+XSHkGfGllqDISDRAWvI5JFU6r1PPv7d b22lJeW+BnheeZDZXm0k =h0Hq -----END PGP SIGNATURE----- --Apple-Mail=_44BBE6AB-A070-4794-A716-1A9712C2128B-- From owner-freebsd-toolchain@FreeBSD.ORG Sun Sep 1 18:04: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 4A76325F; Sun, 1 Sep 2013 18:04:02 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 288C72C43; Sun, 1 Sep 2013 18:04:01 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id F18225606D; Sun, 1 Sep 2013 13:03:50 -0500 (CDT) Date: Sun, 1 Sep 2013 13:03:50 -0500 From: Mark Linimon To: John Baldwin Subject: Re: GCC withdraw Message-ID: <20130901180350.GA12351@lonesome.com> References: <20130822200902.GG94127@funkthat.com> <201308291344.25562.jhb@freebsd.org> <201308301041.18874.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201308301041.18874.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "Sam Fourman Jr." , Boris Samorodov , FreeBSD Current , 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: Sun, 01 Sep 2013 18:04:02 -0000 On Fri, Aug 30, 2013 at 10:41:18AM -0400, John Baldwin wrote: > So my take away from this is that you have no plans to support any platform > that doesn't support clang as you just expect ia64 and sparc64 to die and > not be present in 11.0. That may be the best path, but I've certainly not > seen that goal discussed publically. If this is the case, IMHO: - it's a decision to be made by the project as a whole, not just one individual; - if the decision is made, there should be one major release cycle before it's done; - our userbase (admittedly small) should have a heads-up that they will have to migrate after that timeframe. fwiw, unlike alpha, which was withdrawn because it had ceased to function, sparc64 and ia64 work and have active developer(s), so I don't think it would be entirely fair to cite its removal as a precedent. tl;dr: just because you don't use these boxes doesn't mean others don't. mcl From owner-freebsd-toolchain@FreeBSD.ORG Sun Sep 1 18:28: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 CBAADD95; Sun, 1 Sep 2013 18:28:16 +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 8DA3D2D7B; Sun, 1 Sep 2013 18:28:16 +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 r81ISDb0030899 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 1 Sep 2013 18:28:14 GMT (envelope-from theraven@freebsd.org) Content-Type: multipart/signed; boundary="Apple-Mail=_4D3FE985-F61C-4EEB-9489-02A9A8DA380F"; 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: <20130901180350.GA12351@lonesome.com> Date: Sun, 1 Sep 2013 19:28:07 +0100 Message-Id: <6668F65C-812F-4069-83CE-7F8CF3316527@freebsd.org> References: <20130822200902.GG94127@funkthat.com> <201308291344.25562.jhb@freebsd.org> <201308301041.18874.jhb@freebsd.org> <20130901180350.GA12351@lonesome.com> To: Mark Linimon X-Mailer: Apple Mail (2.1508) Cc: "Sam Fourman Jr." , toolchain@freebsd.org, Boris Samorodov , FreeBSD Current , John Baldwin 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: Sun, 01 Sep 2013 18:28:17 -0000 --Apple-Mail=_4D3FE985-F61C-4EEB-9489-02A9A8DA380F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 1 Sep 2013, at 19:03, Mark Linimon wrote: > If this is the case, IMHO: I was going to quote the whole mail, but actually this is enough. As I = have already said in this thread, there is no such plan. I repeat, for = those who missed it the first time: On 30 Aug 2013, at 16:11, David Chisnall wrote: > I am not proposing: >=20 > ... >=20 > - To deprecate any architectures >=20 > - To break any architectures If a platform ends up without a working toolchain in a few years and = there is no way (LLVM, recent GCC, heavily patched old GCC, = vendor-supplied toolchain) of building it, then we will have to make the = decision about its future. Whether that means getting the Foundation = and / or some other interested body to pay for someone to work on a = toolchain or dropping support is an issue for stakeholders in the = platform. =20 We will probably have to make this call about at least IA64 in a couple = of years, and possibly some PowerPC and SPARC variants, but it's not a = decision that needs to be made any time soon. I know SemiHalf does a = lot of embedded FreeBSD work with PowerPC and a few people do with = SPARC, so there are definitely people with vested interests in = maintaining those two platforms. I'd honestly be surprised if IA64 is = around in two years (mind you, I've been expecting it to die for the = last five, so I'm willing to be surprised again), but maybe there will = be a lot of cheap second-hand IA64 hardware on the market as all of the = big customers switch to something else reviving interest in the = platform... David --Apple-Mail=_4D3FE985-F61C-4EEB-9489-02A9A8DA380F 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 iQIcBAEBAgAGBQJSI4c3AAoJEKx65DEEsqId/t0QAK8V0kucd+YxPgwnZbTbQNjf KQyBumy1fB1I8CV6lQEXAZILaFhKTiAKQW6V4UVOxtcQ30+7BJVAyN1zBNZ6Qhra VG9XZZJP0M+n4SLRAGOhhfSuLvLNNg0dD9XDnft8W2kBzyG+pBo36n28wuCzhP8Z WB1ieh2mHQHB3whEKRfNDyFX8Fd3tq+p5Ieh+jqjQk8XEk6M0Ska/D7aqZ024wPE b2UxKIeejn5IV19RrJrturjQCzPPUAw48m/GCmOqO6wSZzHU0EA/WSglfad/dJUg 6EOjWDDsO4b1sprmPG5/bXd+8RXhuUTlgOFAgsJBjtqcqjVxzXmj+68CWUdKVmTl RThtVrDDxFDFvkwjxF1LgichoiJCQWBNZKtPCrmGnleoA0x0PY4qQiC5mFpWKSGY VaV3m6nTh6jizY9fPA3SAtEy/BMu7PAj1XEUAhTLB51a+yGRVVIzABEsNzbJukrz aZRCGZAFS4nh1V7FR4R+jM2dcH2Gi0J69m0lL/2aOj4jd+U4l6BoHT/RWVu0lho2 OtMPKF0FNnDtwWP6wQTxWHp6RcJqFkQ3CX0ch72/utrGWBYAvz2pXm/Q/O6hCN5a MveWpnRzh9auQ9HfHiLhvOVBHYR1t22YbNWGlsAezzqysQnwSeOwpL/Rj7HrNHj5 mquydzvEKLe3Zx3UXCYk =3g0T -----END PGP SIGNATURE----- --Apple-Mail=_4D3FE985-F61C-4EEB-9489-02A9A8DA380F-- From owner-freebsd-toolchain@FreeBSD.ORG Sun Sep 1 18:44:44 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 611653B8 for ; Sun, 1 Sep 2013 18:44:44 +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 2E2A02EF4 for ; Sun, 1 Sep 2013 18:44:43 +0000 (UTC) Received: by mail-ie0-f175.google.com with SMTP id u16so6655201iet.20 for ; Sun, 01 Sep 2013 11:44:37 -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=bai4YSfpLQFf1xTxGzwWNzwRv7xW7gAB6YYm1JabCQI=; b=IYISZeM4vU7Li9CVkurbSOC5/togYaKBbBQM1pJGueBwrkpJQCykvk1cKJa7phGJn4 lia67VcXuz0f6HIANdmeX+nsdbBTiEcRnVIa1N+SCoUcf+2OyxZGAQyt/jQd3vX1qdAt l1DXFCgRs07GLkIadaMpr+aiTghQxxqGHqiibWwuDlYxjwbsM6Ak4I5OaoXiHT9iFVc6 zAfQOooG+zfuBhS/RjCviTOF6fEQrcnyfvnky8L2NAfVhl/vCNOp+lqngr7dQjdYBfGg 2YGZlVQmbY2EsrmFEPzcgoz6bioa927NP74i/QKgdhW078VTQ2cCO8pU2Y+TTIpdAKj/ dJvw== X-Gm-Message-State: ALoCoQncioOQL6j7zEstU5bU4Pjc8Gllfiw86t5N4MRgkV74YASryG7iFvVlucClOwt3zuru2JOb X-Received: by 10.50.39.18 with SMTP id l18mr9508845igk.4.1378061077526; Sun, 01 Sep 2013 11:44:37 -0700 (PDT) Received: from [10.0.0.53] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id x6sm18887051igb.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 01 Sep 2013 11:44:36 -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: <20130901180350.GA12351@lonesome.com> Date: Sun, 1 Sep 2013 12:44:32 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <81EF1224-CA6C-43AD-9364-3D8CD418951D@bsdimp.com> References: <20130822200902.GG94127@funkthat.com> <201308291344.25562.jhb@freebsd.org> <201308301041.18874.jhb@freebsd.org> <20130901180350.GA12351@lonesome.com> To: Mark Linimon X-Mailer: Apple Mail (2.1085) Cc: "Sam Fourman Jr." , toolchain@freebsd.org, Boris Samorodov , FreeBSD Current , John Baldwin 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: Sun, 01 Sep 2013 18:44:44 -0000 On Sep 1, 2013, at 12:03 PM, Mark Linimon wrote: > On Fri, Aug 30, 2013 at 10:41:18AM -0400, John Baldwin wrote: >> So my take away from this is that you have no plans to support any = platform >> that doesn't support clang as you just expect ia64 and sparc64 to die = and >> not be present in 11.0. That may be the best path, but I've = certainly not >> seen that goal discussed publically. >=20 > If this is the case, IMHO: >=20 > - it's a decision to be made by the project as a whole, not just one > individual; >=20 > - if the decision is made, there should be one major release cycle > before it's done; >=20 > - our userbase (admittedly small) should have a heads-up that they > will have to migrate after that timeframe. >=20 > fwiw, unlike alpha, which was withdrawn because it had ceased to = function, > sparc64 and ia64 work and have active developer(s), so I don't think = it > would be entirely fair to cite its removal as a precedent. >=20 > tl;dr: just because you don't use these boxes doesn't mean others = don't. I'm working on a set of ports that can be installed so you can use the = external toolchain support in the tree... But it is being a pain since = there turns out to be some unexpected interdependencies and ordering = that's tricky to get right. But this does mean I've extracted the FreeBSD specific changes into a = series of patches... Warner From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 2 19:40: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 903DB7D5 for ; Mon, 2 Sep 2013 19:40:31 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay001.isp.belgacom.be (mailrelay001.isp.belgacom.be [195.238.6.51]) by mx1.freebsd.org (Postfix) with ESMTP id 27D802DB9 for ; Mon, 2 Sep 2013 19:40:30 +0000 (UTC) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AswLAGvoJFJbsU3F/2dsb2JhbABagwd6rl4BkzsXdIMBXzQqiD2YIKB6kByEBwOQI4dRkWeDIjo Received: from 197.77-177-91.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([91.177.77.197]) by relay.skynet.be with ESMTP; 02 Sep 2013 21:40:29 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.14.7/8.14.7) with ESMTP id r82JeShA058616 for ; Mon, 2 Sep 2013 21:40:28 +0200 (CEST) (envelope-from tijl@FreeBSD.org) Date: Mon, 2 Sep 2013 21:40:24 +0200 From: Tijl Coosemans To: toolchain@FreeBSD.org Subject: clang -fprofile-generate Message-ID: <20130902214024.2af1096d@kalimero.tijl.coosemans.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/Qsn84yBS0B2iNkemX64=CcR"; protocol="application/pgp-signature" 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: Mon, 02 Sep 2013 19:40:31 -0000 --Sig_/Qsn84yBS0B2iNkemX64=CcR Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, I was trying to build multimedia/x264 using clang as follows: In the Makefile remove USE_GCC=3Dany. In option dialog on leave PGO on. It ends in the following linker error: cc -o x264 x264.o input/input.o input/timecode.o input/raw.o input/y4m.o o= utput/raw.o output/matroska.o output/matroska_ebml.o output/flv.o output/fl= v_bytestream.o filters/filters.o filters/video/video.o filters/video/source= .o filters/video/internal.o filters/video/resize.o filters/video/cache.o fi= lters/video/fix_vfr_pts.o filters/video/select_every.o filters/video/crop.o= filters/video/depth.o input/thread.o libx264.a -m32 -fstack-protector -= fstack-protector -L/usr/local/lib -lm -pthread -fprofile-generate /usr/bin/ld: /usr/bin/../lib/libprofile_rt.a: No such file: No such file or= directory cc: error: linker command failed with exit code 1 (use -v to see invocation) Isn't libprofile_rt.a included with the base system llvm? --Sig_/Qsn84yBS0B2iNkemX64=CcR Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iF4EAREIAAYFAlIk6awACgkQfoCS2CCgtivwjAD/YuM6UkG3rbJQYcQEZdG/UHw9 ZG8dAXrh9fWFOgE6hAkA/jFQg2CnB4ZIKselM6UJ4Mj2dHnWkkxLIJkxs05TEYpv =DWSH -----END PGP SIGNATURE----- --Sig_/Qsn84yBS0B2iNkemX64=CcR-- From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 2 20: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 2746C186; Mon, 2 Sep 2013 20:04:34 +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 DBD802F3A; Mon, 2 Sep 2013 20:04:33 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::516e:d65:dc6:78f8] (unknown [IPv6:2001:7b8:3a7:0:516e:d65:dc6:78f8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 666D25C44; Mon, 2 Sep 2013 22:04:20 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_932AA156-535F-49F8-A661-54D54F48E6CB"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: clang -fprofile-generate From: Dimitry Andric In-Reply-To: <20130902214024.2af1096d@kalimero.tijl.coosemans.org> Date: Mon, 2 Sep 2013 22:04:07 +0200 Message-Id: References: <20130902214024.2af1096d@kalimero.tijl.coosemans.org> To: Tijl Coosemans X-Mailer: Apple Mail (2.1508) 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: Mon, 02 Sep 2013 20:04:34 -0000 --Apple-Mail=_932AA156-535F-49F8-A661-54D54F48E6CB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Sep 2, 2013, at 21:40, Tijl Coosemans wrote: > I was trying to build multimedia/x264 using clang as follows: > In the Makefile remove USE_GCC=3Dany. > In option dialog on leave PGO on. >=20 > It ends in the following linker error: >=20 > cc -o x264 x264.o input/input.o input/timecode.o input/raw.o = input/y4m.o output/raw.o output/matroska.o output/matroska_ebml.o = output/flv.o output/flv_bytestream.o filters/filters.o = filters/video/video.o filters/video/source.o filters/video/internal.o = filters/video/resize.o filters/video/cache.o filters/video/fix_vfr_pts.o = filters/video/select_every.o filters/video/crop.o filters/video/depth.o = input/thread.o libx264.a -m32 -fstack-protector -fstack-protector = -L/usr/local/lib -lm -pthread -fprofile-generate > /usr/bin/ld: /usr/bin/../lib/libprofile_rt.a: No such file: No such = file or directory > cc: error: linker command failed with exit code 1 (use -v to see = invocation) >=20 > Isn't libprofile_rt.a included with the base system llvm? Nope, not currently. Last time I tried building it, it didn't yet work properly. The library gets used in at link time, but I don't see where any entry point to it gets called. I did not have time yet to take a deeper look at it. For now, profile generation should be disabled for x264. -Dimitry --Apple-Mail=_932AA156-535F-49F8-A661-54D54F48E6CB 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.20 (Darwin) iEYEARECAAYFAlIk70EACgkQsF6jCi4glqPAJgCfX0j0oPUBZ1D/dZz1KVFxMK6t z6kAn0dH8m0p95swHAAuiLvD7emsntwW =KuNm -----END PGP SIGNATURE----- --Apple-Mail=_932AA156-535F-49F8-A661-54D54F48E6CB-- From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 2 20:15:14 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 7875C3B3; Mon, 2 Sep 2013 20:15:14 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e: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 4E7D72FAC; Mon, 2 Sep 2013 20:15:14 +0000 (UTC) Received: by mail-pb0-f51.google.com with SMTP id jt11so5062876pbb.38 for ; Mon, 02 Sep 2013 13:15:14 -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:content-transfer-encoding; bh=zlRyL4hjFRxvcwHGjq223cD1zIEsoo7opHT56T3FC6o=; b=R7mqESOsIpbxiGq5b3t54d1SNXoAIcRrZqRJY3DbMJ2y4wnrAzA/Oc5QZ/zynkt3X+ vCXKZbwCIcdUzQbUQHXwBvE+m/x1xmd9eYZaMlsvLZ6WOnEGWSOn4fI2Bv7ptx1ZbMfg QYYY6KB79oQ+BktQ28EcYjGrlvCiZuTmgBu82GfIeXKAY7WiF5t2V8jCdaLrPMj87VJi qERxEB8ck3pIRH76VEqw/QRPI39FATOFt9NnSxjQCXkEOgYoAL7vKVSnXlmdlVZilHVV iYgxDwiUVL5HRxLJ5wpavw2i+bskbWWtuNkcdrwQ4OrrtqdKzldGcEktMrl4BJuocbCa M0iA== MIME-Version: 1.0 X-Received: by 10.68.182.225 with SMTP id eh1mr3723044pbc.172.1378152913924; Mon, 02 Sep 2013 13:15:13 -0700 (PDT) Received: by 10.68.129.99 with HTTP; Mon, 2 Sep 2013 13:15:13 -0700 (PDT) In-Reply-To: <20130902214024.2af1096d@kalimero.tijl.coosemans.org> References: <20130902214024.2af1096d@kalimero.tijl.coosemans.org> Date: Mon, 2 Sep 2013 16:15:13 -0400 Message-ID: Subject: Re: clang -fprofile-generate From: "illoai@gmail.com" To: Tijl Coosemans Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Mon, 02 Sep 2013 20:15:14 -0000 On 2 September 2013 15:40, Tijl Coosemans wrote: > Hi, > > I was trying to build multimedia/x264 using clang as follows: > In the Makefile remove USE_GCC=3Dany. > In option dialog on leave PGO on. > > It ends in the following linker error: > > cc -o x264 x264.o input/input.o input/timecode.o input/raw.o input/y4m.o= output/raw.o output/matroska.o output/matroska_ebml.o output/flv.o output/= flv_bytestream.o filters/filters.o filters/video/video.o filters/video/sour= ce.o filters/video/internal.o filters/video/resize.o filters/video/cache.o = filters/video/fix_vfr_pts.o filters/video/select_every.o filters/video/crop= .o filters/video/depth.o input/thread.o libx264.a -m32 -fstack-protector = -fstack-protector -L/usr/local/lib -lm -pthread -fprofile-generate > /usr/bin/ld: /usr/bin/../lib/libprofile_rt.a: No such file: No such file = or directory > cc: error: linker command failed with exit code 1 (use -v to see invocati= on) > > Isn't libprofile_rt.a included with the base system llvm? -CURRENT or -STABLE? It seems to only exist here (9.2-RC3 amd64) as /usr/local/lib/libprofile_rt.a which is installed by devel/llvm-devel (3.4-something). --=20 --