From owner-freebsd-toolchain@FreeBSD.ORG Sat Jun 25 16:40:11 2011 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F34131065678 for ; Sat, 25 Jun 2011 16:40:11 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id B133F8FC12 for ; Sat, 25 Jun 2011 16:40:11 +0000 (UTC) Received: from 63.imp.bsdimp.com (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p5PGaK7A033632 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Sat, 25 Jun 2011 10:36:20 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Sat, 25 Jun 2011 10:36:02 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <12B50B3F-88E0-430D-AB67-FBC1BC4373B1@bsdimp.com> References: <0C35FE0F-3301-44C6-AC40-233F6C446EBC@gmail.com> To: Gerald Pfeifer X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Sat, 25 Jun 2011 10:36:20 -0600 (MDT) Cc: toolchain@freebsd.org Subject: Re: ARM issue with old binutils X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Jun 2011 16:40:12 -0000 On Jun 25, 2011, at 9:16 AM, Gerald Pfeifer wrote: > On Wed, 22 Jun 2011, Damjan Marion wrote: >> I see 3 options to fix this: >>=20 >> 1. Ask clang folks to patch llvm to use old mnemonics ("mov r0, r0, = rrx" instead of "rrx r0,r0") >> 2. Maintain same patch for freebsd only >> 3. patch binutils to support this new mnemonics >=20 > 4. Finally upgrade to a modern version of binutils. >=20 > Yes, I know that is GPLv3. Been there, done that, and it is not a = problem=20 > at all, just FUD. IBM, SAP, Oracle, and all the others are not = concerned > about GPLv3 in the toolchain, nor should we. Except for FUD. Except there *ARE* FreeBSD users that have said that it is a real = problem for them. It isn't FUD. The project has adopted the policy in = reaction to large commercial FreeBSD users that have very restrictive = company policies driven by their legal department's evaluation of GPLv3. Warner