From owner-freebsd-arm@FreeBSD.ORG Tue Sep 30 14:07:51 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 31E2A224 for ; Tue, 30 Sep 2014 14:07:51 +0000 (UTC) Received: from nibbler.fubar.geek.nz (nibbler.fubar.geek.nz [199.48.134.198]) by mx1.freebsd.org (Postfix) with ESMTP id 144B0FAB for ; Tue, 30 Sep 2014 14:07:50 +0000 (UTC) Received: from bender.lan (97e07ab1.skybroadband.com [151.224.122.177]) by nibbler.fubar.geek.nz (Postfix) with ESMTPSA id 1CB355CF51; Tue, 30 Sep 2014 14:07:49 +0000 (UTC) Date: Tue, 30 Sep 2014 15:07:43 +0100 From: Andrew Turner To: Warner Losh Subject: Re: MK_ARM_EABI to retire in current Message-ID: <20140930150743.15999c12@bender.lan> In-Reply-To: References: <20140928121818.741e7e7e@bender.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 14:07:51 -0000 On Sun, 28 Sep 2014 10:19:09 -0700 Warner Losh wrote: > > On Sep 28, 2014, at 4:18 AM, Andrew Turner > wrote: > > > On Mon, 19 May 2014 09:40:33 -0600 > > Warner Losh wrote: > > > >> Greetings, > >> > >> MK_ARM_EABI is going to die in current. It is the default for all > >> platforms currently. I’m eliminating it as a build option. It must > >> die because it invisibly (to uname) effects the ABI. > >> > >> So, to that end, I see two options: > >> > >> (1) Retire and remove oabi support. > >> (2) Retain oabi support, but change its name to armo and armoeb. > >> > >> The rough consensus of arm developers I’ve polled now, and in the > >> past, is that we just let oabi support die now that EABI support is > >> working for everybody. > >> > >> Before I pull the trigger on this, however, I must ask if anybody > >> has a problem with my doing option (1), and if so, what keeps you > >> using oabi. > >> > >> Comments? > > > > As far as I know all the problems with ARM EABI on armeb mentioned > > in this thread have been fixed. I think we should now retire the > > oabi support and remove MK_ARM_EABI. > > I’m game. I think we should move forward on option #1. We’ve had no > issues in the 10.1 release related to this that I’m aware of. Should > there be no further objections, my plan is to move forward with this > later this week. I've created a change for review at [1]. Andrew [1] https://reviews.freebsd.org/D876