public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Chris Metcalf <cmetcalf@mellanox.com>, libc-alpha@sourceware.org
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: RFC: remove the "tile" architecture from glibc
Date: Mon, 04 Dec 2017 18:36:00 -0000	[thread overview]
Message-ID: <d63acdc5-6f01-7839-77d7-8c5dac1b16a1@linaro.org> (raw)
In-Reply-To: <332ee880-e770-eff9-66cb-ff41a2b649bf@mellanox.com>



On 04/12/2017 16:13, Chris Metcalf wrote:
> On 12/4/2017 6:10 AM, Adhemerval Zanella wrote:
>> Now back to thread topic, Chris Metcalf gave us some indications that
>> tilepro userbase and support do not justify the maintaining effort.  It
>> already has kernel ABI incompatibilities (for instance ca768667d873 fix on
>> linux and some atomic unsupported operations that broke the build on
>> recent glibc fixes).  I think we could at least remove old tilepro
>> support.
> 
> That's certainly a plausible middle ground.   Of course, tilepro support is
> only 30 files (about half of which are just *.abilist files) out of 204 total
> files for tile support, so the tree won't benefit as much from that cleanup.
> But we have heard some support for tilegx, and none for tilepro, so maybe
> that's a plausible position to land, particularly given the Debian interest.

We maintain a buildbot for all current supported architectures [1], which
means less computing resources being spent in build/checking in this
specific case.  As Joseph has put, tilepro removal will most likely incur
in some internal tile folder simplification.

[1] https://sourceware.org/ml/libc-testresults/

> 
> For what it's worth, what I've heard from kernel maintainers suggests that
> just marking tile as "Orphan" in the MAINTAINERS file and not deleting
> any of the existing code is the right position in that community.
> 

  reply	other threads:[~2017-12-04 18:36 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
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 [this message]
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>
     [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
2018-02-01 13:34           ` Adhemerval Zanella
2018-02-01 13:50             ` Joseph Myers
2018-02-01 16:50               ` Adhemerval Zanella
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=d63acdc5-6f01-7839-77d7-8c5dac1b16a1@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=cmetcalf@mellanox.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --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).