public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Chris Metcalf <cmetcalf@mellanox.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: RFC: remove the "tile" architecture from glibc
Date: Fri, 01 Dec 2017 21:57:00 -0000	[thread overview]
Message-ID: <d6c8e425-a6b6-6594-05e3-965536f06da3@physik.fu-berlin.de> (raw)
In-Reply-To: <1a57be83-3349-5450-ee4f-d2a33569a728@mellanox.com>

Hi Chris!

On 12/01/2017 10:34 PM, Chris Metcalf wrote:
> The tile architecture was introduced to glibc in 2011 and first
> appeared in glibc 2.15.  The chip family of TILEPro and TILE-Gx was
> developed by Tilera, which was eventually acquired by Mellanox.  Now
> at Mellanox we are developing new chips based on the ARM64
> architecture; our last TILE-Gx chip (the Gx72) was released in 2013,
> and our customers using the tile architecture products are now all in
> maintenance mode, as far as we know, and not looking to upgrade their
> software to newer open-source releases.

This feels very odd. It isn't been very long until I heard about TileGX
for the first time when I saw a talk by a Japanese Debian guy who showed
me his efforts to get Debian running on a small router with impressive
performance [1]. The board built gcc natively in just about two hours.

Tile has also been added to Debian Rebootstrap and it's currently possible
to bootstrap for this architecture from source. The Jenkins job shows
that this currently is successful.

> Compounding this state of affairs is the fact that after twelve years
> here I am moving on next week; my last day at Mellanox is December
> 8th.  Since tracking upstream development of the old tile architecture
> is not a high priority for Mellanox, reasonably enough, it seems
> cleanest at this point to propose removal of the architecture from the
> glibc tree, so that the 2.26 release will be the last release to have
> tile support.

But why should it be only up to Mellanox whether support for Tile is
part of glibc or not. I find straight up removal a bit too strong,
especially since QEMU supports Tile as well. I think the first step
should just be to mark the Tile port of glibc as unmaintained but not
remove it altogether. That could be too frustrating for people using
it. I'm pretty sure that there are more than just Mellanox' customers
who are using Linux on Tile.

> If there is any desire to continue to support the tile architecture in
> glibc, I'm happy to hand off to someone else as maintainer.  I'm aware
> of one issue in the current code, which is that upstream gcc vector
> insn support has a bug in it that causes some of the string functions
> to misbehave; I can publish a fix for that before handing off, if desired.

Yes, that would be great. If it's a known bug and there is a known,
working fix, it would be great if it could be merged upstream and
Tile support be kept for a while for the people hacking on Debian
on Tile.

> I will in any case be dropping off the glibc list (other than perhaps
> occasionally reading the archives) at the end of next week.  It's been
> a rewarding experience following glibc's development over the last six
> years and I will certainly miss being part of this community.

And here I am just having joined the list, this being one of the first
things too read :/.

> I'm keeping that libc.so.6 sticker I got from Carlos, though!  :)

Adrian

> [1] https://mikrotik.com/product/CCR1009-7G-1C-1SplusPC
> [2] https://jenkins.debian.net/view/rebootstrap/

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  parent reply	other threads:[~2017-12-01 21:57 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 21:34 Chris Metcalf
2017-12-01 21:41 ` Joseph Myers
2017-12-01 21:57 ` John Paul Adrian Glaubitz [this message]
2017-12-01 22:11   ` Joseph Myers
2017-12-01 22:30     ` John Paul Adrian Glaubitz
2017-12-01 22:41       ` Joseph Myers
2017-12-02 15:15         ` John Paul Adrian Glaubitz
2017-12-04 11:10           ` Adhemerval Zanella
2017-12-04 11:28             ` John Paul Adrian Glaubitz
2017-12-04 18:03             ` Joseph Myers
2017-12-04 18:32               ` Adhemerval Zanella
2017-12-04 18:55                 ` Joseph Myers
2017-12-04 18:14             ` Chris Metcalf
2017-12-04 18:36               ` Adhemerval Zanella
2017-12-04 17:53           ` Joseph Myers
2017-12-04 18:47             ` John Paul Adrian Glaubitz
2017-12-04 19:02               ` Joseph Myers
     [not found]       ` <alpine.DEB.2.20.1801311732001.23883@digraph.polyomino.org.uk>
     [not found]         ` <38170271-e17f-0a7e-7dd2-06fa6ddfae62@physik.fu-berlin.de>
2018-02-01 13:34           ` Adhemerval Zanella
2018-02-01 13:50             ` Joseph Myers
2018-02-01 16:50               ` Adhemerval Zanella
     [not found]           ` <9f8b994a-7085-e263-dd1b-bea2def55fb0@linaro.org>
2018-02-01 13:24             ` Adhemerval Zanella
2018-02-01 13:33               ` John Paul Adrian Glaubitz
2018-02-01 13:37                 ` Adhemerval Zanella
2018-02-01 13:45                   ` Joseph Myers
2018-02-01 16:40                     ` Adhemerval Zanella
2018-02-01 13:39               ` Joseph Myers
2018-02-01 17:21                 ` Adhemerval Zanella
2018-02-01 17:52                   ` Joseph Myers
2018-02-01 18:30                   ` Joseph Myers
2018-02-14 18:13             ` Joseph Myers
2017-12-02  1:15   ` Chris Metcalf
2017-12-02 15:16     ` John Paul Adrian Glaubitz
2017-12-04 21:49       ` Chris Metcalf
2017-12-04 23:29         ` Joseph Myers
2018-03-07 15:39       ` Arnd Bergmann
2018-03-07 16:01         ` Joseph Myers
2018-03-07 16:08           ` John Paul Adrian Glaubitz
2018-03-07 16:49             ` Adhemerval Zanella
2018-03-07 17:17               ` Joseph Myers
2018-03-07 18:16         ` Helmut Grohne
2018-03-08 15:55           ` Arnd Bergmann
2018-03-08 16:06             ` John Paul Adrian Glaubitz
2018-03-08 16:23               ` Arnd Bergmann
2018-03-09 16:31               ` Joseph Myers
2018-03-09 16:37                 ` John Paul Adrian Glaubitz
2018-03-09 16:53                   ` Joseph Myers
2018-03-08 17:14             ` Palmer Dabbelt
2018-03-08 23:36               ` Arnd Bergmann
2017-12-02  3:24 ` Carlos O'Donell
2017-12-08 16:20 ` Chris Metcalf
2018-01-05  9:01 ` Henrik Grindal Bakken

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d6c8e425-a6b6-6594-05e3-965536f06da3@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=cmetcalf@mellanox.com \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).