mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Rich Felker <dalias@libc.org>
Cc: Rob Landley <rob@landley.net>, <musl@lists.openwall.com>,
	<libc-alpha@sourceware.org>, <linux-sh@vger.kernel.org>
Subject: Re: SH sigcontext ABI is broken
Date: Wed, 24 Jun 2015 19:37:45 +0000	[thread overview]
Message-ID: <alpine.DEB.2.10.1506241934590.30125@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20150624181235.GU1173@brightrain.aerifal.cx>

On Wed, 24 Jun 2015, Rich Felker wrote:

> On Wed, Jun 24, 2015 at 02:10:06PM +0000, Joseph Myers wrote:
> > On Wed, 24 Jun 2015, Rich Felker wrote:
> > 
> > > Nominally SH3 support remains in both the kernel and glibc. If it can
> > > be established that multiple parties agree that there's really no one
> > > left who cares about the old no-FPU sigcontext ABI on SH3, I will be
> > > all for dropping it and unifying sigcontext.
> > 
> > Note that right now we have BE and LE versions of *three* ABIs for SH in 
> > glibc (SH3 soft-float, SH4 soft-float, SH4 hard-float) (and as noted in 
> > this discussion, right now each would only work properly on a kernel with 
> > the corresponding configuration).  See 
> > <https://sourceware.org/glibc/wiki/ABIList>.
> 
> Is your understanding that SH4 soft-float is using the SH4 ucontext_t
> layout? I don't think it's even working at all. Glibc uses the layout

My understanding is what Kaz affirmed in 
<https://sourceware.org/ml/libc-alpha/2014-01/msg00388.html>.  It's 
entirely possible there are bugs (including regressions) in this area; if 
so, they should be filed in Bugzilla.

-- 
Joseph S. Myers
joseph@codesourcery.com


  parent reply	other threads:[~2015-06-24 19:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  7:09 Rich Felker
2015-06-19  7:41 ` Andreas Schwab
2015-06-19 19:12   ` Rich Felker
2015-06-19 19:57     ` [musl] " Andreas Schwab
2015-06-19 20:32       ` Rich Felker
2015-06-20  8:10         ` [musl] " Geert Uytterhoeven
2015-06-20 19:59           ` Rob Landley
2015-07-02 19:23             ` Maciej W. Rozycki
2015-07-02 22:51               ` Rob Landley
2015-07-03  6:43                 ` Andreas Schwab
2015-06-20 18:06 ` Rich Felker
2015-06-24  4:25   ` [musl] " Rob Landley
2015-06-24  4:52     ` Rich Felker
2015-06-24  7:12       ` [musl] " Rob Landley
2015-06-24 18:03         ` Rich Felker
2015-06-24  8:40           ` [musl] " Rob Landley
2015-06-24 21:34             ` Rich Felker
2015-06-24 22:32               ` Rob Landley
2015-06-24 23:26                 ` Bobby Bingham
2015-06-24 23:54                 ` Rich Felker
2015-06-25  6:24               ` [musl] " Geert Uytterhoeven
2015-06-24 14:10       ` Joseph Myers
2015-06-24  8:23         ` Rob Landley
2015-06-24 18:12         ` Rich Felker
2015-06-24  9:14           ` Rob Landley
2015-06-24 22:02             ` Rich Felker
2015-06-24 19:37           ` Joseph Myers [this message]
2015-06-24 20:08             ` Rich Felker

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.10.1506241934590.30125@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=dalias@libc.org \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=musl@lists.openwall.com \
    --cc=rob@landley.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).