public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: RFC: remove the "tile" architecture from glibc
Date: Mon, 04 Dec 2017 18:32:00 -0000	[thread overview]
Message-ID: <2f17cd21-598f-97c9-215c-1a4e533629d7@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1712041756490.16372@digraph.polyomino.org.uk>



On 04/12/2017 16:03, Joseph Myers wrote:
> On Mon, 4 Dec 2017, Adhemerval Zanella wrote:
> 
>> GCC version which does not support m68k (I do not think we have a policy
>> to remove deprecated architecture in GCC latest version where there is still
>> compiler support in older releases).
> 
> In my view, if GCC removes support for an architecture I think that's 
> sufficient basis for obsoleting it in glibc as well rather than waiting a 
> few more years in which it becomes increasingly hard for people to test 
> changes build on that architecture because of the need to use a different 
> GCC version there.  However, we don't need to decide this now, as while 
> there are suggestions of obsoleting non-cc0 or non-LRA architectures, 
> nothing has happened yet in that regard (and even if non-cc0 architectures 
> were obsoleted for GCC 8, the removal probably wouldn't be until after GCC 
> 8 branched, so until then we'd just add --enable-obsolete to the GCC 
> configure options for such architectures in build-many-glibcs.py).

I personally think it is too restrictive to remove the architecture in
such case if the minimum glibc required GCC version still provides support. 
I give you that it incur in a more troublesome testing because one will
need to pick an subset of supported compiler version, but in such case
we can set a policy of architecture being 'deprecated' and schedule for
future removal (maybe in a subsequent glibc release).

> 
>> 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. 
> 
> Certainly we can come to separate conclusions about obsoletion for tilegx 
> and tilepro.  (Preferably obsoleting tilepro would mean the sysdeps 
> directory structure then being simplified to avoid the unnecessary 
> directory levels in tile/tilegx, just as after obsoleting ARM old-ABI I 
> eliminated the eabi/ subdirectories.)
> 

I think this sounds like a plan for 2.27. I will try to spend some cycles
on this in following weeks.

  reply	other threads:[~2017-12-04 18:32 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 [this message]
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>
     [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=2f17cd21-598f-97c9-215c-1a4e533629d7@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=joseph@codesourcery.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).