From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43132) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1euJhz-0007UT-4X for qemu-devel@nongnu.org; Fri, 09 Mar 2018 10:13:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1euJhu-0002iL-Tk for qemu-devel@nongnu.org; Fri, 09 Mar 2018 10:13:23 -0500 Received: from mail-wr0-x236.google.com ([2a00:1450:400c:c0c::236]:44343) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1euJhu-0002hu-L1 for qemu-devel@nongnu.org; Fri, 09 Mar 2018 10:13:18 -0500 Received: by mail-wr0-x236.google.com with SMTP id v65so9336026wrc.11 for ; Fri, 09 Mar 2018 07:13:18 -0800 (PST) References: <0304e590-ab51-649b-7cee-bb7c5be6f5e4@redhat.com> From: Alex =?utf-8?Q?Benn=C3=A9e?= In-reply-to: Date: Fri, 09 Mar 2018 15:13:16 +0000 Message-ID: <87y3j1jn8z.fsf@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Deprecate tilegx ? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bastian Koppelmann Cc: Thomas Huth , Peter Maydell , QEMU Developers , Guan Xuetao , Chen Gang , Chen Gang , Chen Gang , Richard Henderson Bastian Koppelmann writes: > On 02/28/2018 07:11 AM, Thomas Huth wrote: >> On 27.02.2018 12:51, Peter Maydell wrote: >>> I propose that we deprecate and plan to remove the unicore32 code: >> [...] > [...] >> >> Sounds reasonable to me, but let's wait a week or two for feedback from >> Guan Xuetao. > > Agreed. > >> >>> Possibly there are other target architectures we could reasonably >>> deprecate-and-remove (though none of the other ones Linux is dropping >>> in this round are ones we support)... >> >> I'd vote for marking tilegx as deprecated, too, since we even do not >> have an active maintainer for that CPU core (at least I did not spot one >> in our MAINTAINERS file). Opinions? > > I always saw it as a big plus that QEMU supports nearly any > architecture, no matter how obscure it is. So I'm a bit more hesitant on > dropping architectures quickly. All things being equal I agree, however there is a maintenance burden for the QEMU upstream, especially if the only active use if on out-of-tree branches or behind the closed doors of research groups. Looking at https://wiki.qemu.org/Documentation/Platforms/TileGX it doesn't give much of an idea of where I would get toolchains to build guest binaries or what guest user-space I could run. -- Alex Benn=C3=A9e