From: Rob Landley <rob@landley.net>
To: linux-sh@vger.kernel.org
Subject: Re: [musl] SH sigcontext ABI is broken
Date: Wed, 24 Jun 2015 08:23:33 +0000 [thread overview]
Message-ID: <558A6905.7010406@landley.net> (raw)
In-Reply-To: <20150619070912.GA15025@brightrain.aerifal.cx>
On 06/24/2015 09:10 AM, 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>.
>
> We can, of course, choose to declare processor or ABI variants no longer
> supported in glibc, much like we desupported i386 in glibc (requiring i486
> or later - albeit the official desupporting happening several years after
> i386 would no longer build) or removed support for non-EABI ARM. But
> since we don't have an SH maintainer at all in glibc at present, it's
> harder to make such a decision (whereas if an architecture maintainer
> decided some variants were no longer relevant, they could just remove
> support - make those variants give a configure-time error - in the absence
> of someone objecting and willing to take over maintaining support for
> those variants).
>
> I think the next glibc change likely to require action from each
> architecture's maintainer to avoid breaking the build may be Adhemerval's
> cancellation changes - so if no-one comes forward as SH maintainer to at
> least update SH for those changes when they are ready to go in, the build
> for SH will be broken and that will indicate, as per
> <https://sourceware.org/ml/libc-alpha/2015-06/msg00424.html>, that it may
> be time to remove the port from glibc.
Eh, ping me when that happens. I may at least do necessary changes to
keep it building. (Although I can only test glibc on qemu-system-sh4.)
Rob
next prev parent reply other threads:[~2015-06-24 8:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 7:09 SH sigcontext ABI is broken Rich Felker
2015-06-19 7:41 ` Andreas Schwab
2015-06-19 19:12 ` [musl] " Rich Felker
2015-06-19 19:57 ` Andreas Schwab
2015-06-19 20:32 ` Rich Felker
2015-06-20 8:10 ` Geert Uytterhoeven
2015-06-20 18:06 ` [musl] " Rich Felker
2015-06-20 19:59 ` [musl] " Rob Landley
2015-06-24 4:25 ` [musl] " Rob Landley
2015-06-24 4:52 ` Rich Felker
2015-06-24 7:12 ` Rob Landley
2015-06-24 8:23 ` Rob Landley [this message]
2015-06-24 8:40 ` Rob Landley
2015-06-24 9:14 ` Rob Landley
2015-06-24 14:10 ` Joseph Myers
2015-06-24 18:03 ` Rich Felker
2015-06-24 18:12 ` Rich Felker
2015-06-24 19:37 ` Joseph Myers
2015-06-24 20:08 ` Rich Felker
2015-06-24 21:34 ` Rich Felker
2015-06-24 22:02 ` Rich Felker
2015-06-25 6:24 ` Geert Uytterhoeven
2015-07-02 19:23 ` [musl] " Maciej W. Rozycki
2015-07-02 22:51 ` Rob Landley
2015-07-03 6:43 ` Andreas Schwab
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=558A6905.7010406@landley.net \
--to=rob@landley.net \
--cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.