From: Helmut Grohne <helmut@subdivi.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
GNU C Library <libc-alpha@sourceware.org>,
linux-arch <linux-arch@vger.kernel.org>,
metcalf@alum.mit.edu, Henrik Grindal Bakken <hgb@ifi.uio.no>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RFC: remove the "tile" architecture from glibc
Date: Wed, 7 Mar 2018 19:14:07 +0100 [thread overview]
Message-ID: <20180307181407.GA24350@alf.mars> (raw)
In-Reply-To: <CAK8P3a3itR8i2ayG7e4ku7kz+CQU7qHhptdmtmgTz+CzFGmCiw@mail.gmail.com>
On Wed, Mar 07, 2018 at 04:39:47PM +0100, Arnd Bergmann wrote:
> - Helmut Grohne has done the work to add tile-gx to debian
> rebootstrap, and send several patches, as seen in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823167
> However, I could find no information on this actually
> being turned into a full port, or anyone still actively involved
> in it. The Debian rebootstrap page at
> https://wiki.debian.org/HelmutGrohne/rebootstrap
> mentions lots of other architectures, but not this one.
I happened help tilegx, because Adrian found someone with hw and tilegx
appeared to be very well maintained upstream. Very little needed to be
done to make it work in Debian. The patches I sent were pretty generic
and addressed issues that most ports face. What is there allows
constructing most of an essential package set and (unlike a number of
other architectures) bootstrapping tilegx works fairly well. Debian has
a number of source-only ports and tilegx is now one of them.
That said, nobody has taken up the work to proceed a native bootstrap.
Like with nios2, progress is stalled, because the tooling for fully
automating the native phase is missing.
In any case, I won't be able to fix binutils/gcc/glibc/linux issues with
tilegx. So unless someone steps up to do that work, I won't object to
dropping it. It would be sad to see tilegx go, but it certainly isn't my
core interest either.
I'd appreciate a note if it gets dropped from any of these, because I'd
clean up outstanding bug reports then.
The reverse is also true: If you want to see an new architecture in
Debian, I also appreciate an early conversation to avoid duplicating
work.
Hope this helps
Helmut
next prev parent reply other threads:[~2018-03-07 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a57be83-3349-5450-ee4f-d2a33569a728@mellanox.com>
[not found] ` <d6c8e425-a6b6-6594-05e3-965536f06da3@physik.fu-berlin.de>
[not found] ` <abce89d0-6798-069a-1a54-06e664665b78@mellanox.com>
[not found] ` <dc3c52ce-f082-0da0-7828-0d4e6751e2a5@physik.fu-berlin.de>
2018-03-07 15:39 ` RFC: remove the "tile" architecture from glibc Arnd Bergmann
2018-03-07 16:00 ` Joseph Myers
2018-03-07 16:08 ` John Paul Adrian Glaubitz
2018-03-07 18:14 ` Helmut Grohne [this message]
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
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=20180307181407.GA24350@alf.mars \
--to=helmut@subdivi.de \
--cc=arnd@arndb.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hgb@ifi.uio.no \
--cc=libc-alpha@sourceware.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metcalf@alum.mit.edu \
/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