Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758338AbdLRLz5 (ORCPT ); Mon, 18 Dec 2017 06:55:57 -0500 Received: from mail-ot0-f194.google.com ([74.125.82.194]:35352 "EHLO mail-ot0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752817AbdLRLzl (ORCPT ); Mon, 18 Dec 2017 06:55:41 -0500 X-Google-Smtp-Source: ACJfBosiPizSyto4HF+gMxp31sriH+tgEJ20IzC5V/orHEE6ntv+oRl0Dir0YUbdcg0fFOQ+jcH4lHYodt9qXromSkg= MIME-Version: 1.0 In-Reply-To: <20171217222856.2c5937a4@jawa> References: <20171116232239.16823-1-lukma@denx.de> <20171211233625.5689-1-lukma@denx.de> <1513153607.2439.2.camel@Nokia-N900> <20171217204122.0a10a5e1@jawa> <20171217222856.2c5937a4@jawa> From: Arnd Bergmann Date: Mon, 18 Dec 2017 12:55:40 +0100 X-Google-Sender-Auth: QbisB060eyceISbBjiT4_pZUPO0 Message-ID: Subject: Re: [PATCH v5 0/4] ARM: ep93xx: ts72xx: Add support for BK3 board To: Lukasz Majewski Cc: Alexander Sverdlin , Linus Walleij , Hartley Sweeten , Russell King , Linux ARM , Linux Kernel Mailing List , Olof Johansson Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2056 Lines: 50 On Sun, Dec 17, 2017 at 10:28 PM, Lukasz Majewski wrote: > Hi Arnd, > >> On Sun, Dec 17, 2017 at 8:41 PM, Lukasz Majewski >> wrote: >> >> >> We also need to think about upholding support in GCC for >> >> >> ARMv4(t) for the foreseeable future if there is a big web of >> >> >> random deeply embedded systems out there that will need >> >> >> updates. >> >> > >> >> > But we should definitely preserve at least what we have. >> >> >> >> Plain ARMv4 (and earlier) support in gcc is already marked >> >> 'deprecated' and will likely be gone in gcc-8 (it's still there as >> >> of last week). ARMv4T is going to be around for a while, and you >> >> can even keep building for ARMv4 using "-march=armv4t -marm" when >> >> linking with 'ld --fix-v4bx'. >> > >> > I think that we shall start complaining on the gcc-devel mailing >> > list now. >> > >> > I would be hard to wake up in 2 years time and realise that we don't >> > have a modern compiler. >> >> What distro or build system are you using? > > I'm using OE with the "include conf/machine/include/tune-arm920t.inc" > > GCC 7.2 is working Ah wait, this is still for ep93xx, which is always at least armv4t, right? So it won't have a problem with the armv4 deprecation anyway, even the older ep72xx/73xx were ARM720T based and don't have a problem. I'm not entirely sure about their clps711x predecessors, which were some earlier arm7 variant, but Linux doesn't support them any more anyway, and the ARM710T would already be fine without --fix-v4bx. >> It would also be helpful >> to test whether the -march=armv4t/--fix-v4bx workaround produces >> working binaries for you, in that case you could report to the gcc >> developers that the removal of armv4 can continue but that >> the --fix-v4bx option in ld needs to stay around. > > I may ask this issue on OE/Yocto mailing list as well.... To clarify, the only affected platforms are those based on either DEC/Intel StrongARM or Faraday FA526, i.e. EBSA-110, FootBridge, RPC, SA1100, Moxart and Gemini. Arnd