From: David Miller <davem@davemloft.net>
To: adhemerval.zanella@linaro.org
Cc: libc-alpha@sourceware.org
Subject: Re: Remove sparcv8 support
Date: Thu, 20 Oct 2016 20:56:00 -0000 [thread overview]
Message-ID: <20161020.165624.2141018105378735831.davem@davemloft.net> (raw)
In-Reply-To: <48cdf008-b66a-d411-a07a-5a38595978b9@linaro.org>
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date: Thu, 20 Oct 2016 17:47:30 -0200
> The sparcv8 build is broken since GLIBC 2.23 due the new pthread
> barrier implementation [1] and since then there is no thread or
> interest on fixing it (Torvald has suggested some options on
> 2.23 release thread).
It's not lack of interest, it's lack of time.
next prev parent reply other threads:[~2016-10-20 20:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 19:47 Adhemerval Zanella
2016-10-20 20:56 ` David Miller [this message]
2016-10-21 9:02 ` Andreas Larsson
2016-10-21 13:13 ` Adhemerval Zanella
2016-10-21 15:03 ` David Miller
2016-10-24 17:14 ` Torvald Riegel
2016-10-24 17:25 ` Torvald Riegel
2016-10-24 17:43 ` Adhemerval Zanella
2016-10-25 14:34 ` Andreas Larsson
2016-10-25 14:45 ` Adhemerval Zanella
2016-10-26 14:46 ` Andreas Larsson
2016-10-26 18:03 ` Adhemerval Zanella
2016-10-26 18:47 ` David Miller
2016-10-26 19:39 ` Adhemerval Zanella
2016-10-27 10:54 ` Torvald Riegel
2016-10-27 14:36 ` Carlos O'Donell
2016-11-07 16:38 ` David Miller
2016-11-07 21:21 ` Sam Ravnborg
2016-11-08 1:06 ` David Miller
2016-11-09 5:49 ` Sam Ravnborg
2016-11-10 23:33 ` David Miller
2016-11-09 17:08 ` Torvald Riegel
2016-11-09 17:16 ` David Miller
2016-11-10 5:05 ` Torvald Riegel
2016-11-10 16:41 ` Chris Metcalf
2016-11-10 17:08 ` Torvald Riegel
2016-11-10 18:22 ` Chris Metcalf
2016-11-10 23:38 ` Torvald Riegel
2016-10-27 10:38 ` Torvald Riegel
2016-11-01 15:27 ` Andreas Larsson
2016-10-25 14:34 ` Andreas Larsson
2016-10-25 16:22 ` Torvald Riegel
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=20161020.165624.2141018105378735831.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adhemerval.zanella@linaro.org \
--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).