From: Joseph Myers <joseph@codesourcery.com>
To: <davem@davemloft.net>, <libc-alpha@sourceware.org>
Subject: Status of glibc on pre-v9 SPARC
Date: Fri, 15 Dec 2017 17:20:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1712151708540.13157@digraph.polyomino.org.uk> (raw)
Since at least
commit b02840bacdefde318d2ad2f920e50785b9b25d69
Author: Torvald Riegel <triegel@redhat.com>
AuthorDate: Wed Jun 24 14:37:32 2015 +0200
Commit: Torvald Riegel <triegel@redhat.com>
CommitDate: Fri Jan 15 21:20:34 2016 +0100
New pthread_barrier algorithm to fulfill barrier destruction requirements.
building glibc for pre-v9 32-bit SPARC has been broken because
sysdeps/sparc/sparc32/pthread_barrier_wait.c just contains a #error.
Is this something that is still intended to be fixed? Or should pre-v9
32-bit SPARC be considered like the original i386, i.e. too little atomic
operation support so should no longer be supported with v9 being made the
official minimum supported by glibc?
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2017-12-15 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 17:20 Joseph Myers [this message]
2017-12-15 17:45 ` David Miller
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=alpine.DEB.2.20.1712151708540.13157@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=davem@davemloft.net \
--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).