This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] sh: Fix clone exit return code
On Thu, 14 Dec 2017, John Paul Adrian Glaubitz wrote:
> On 12/14/2017 04:48 PM, Joseph Myers wrote:
> > Also, do people interested in sh think the sh3 support is still useful, or
> > is only sh4 support useful now?
> Yes, SH-3 is very useful for the upcoming J-Core J3 CPU , so please
> don't remove support for it.
It would be useful to refactor the sysdeps directories to reduce the need
for separate sh3 and sh4 sysdeps (e.g. why shouldn't they share a single
setjmp implementation with appropriate conditionals?).
My understanding from
<https://sourceware.org/ml/libc-alpha/2014-01/msg00388.html> is that SH3
and SH4 have incompatible ABIs, though I don't know what the differences
are, or whether there are still differences (e.g. at the function call ABI
level) after the kernel sigcontext changes in Linux 4.8 (commit
bbe6c77857c38f4acbdc4fc70399515226d1859a) and consequent glibc changes
> >  http://j-core.org/roadmap.html
That refers to SH3 hard float. Does that mean more SH ABI variants are
coming (if ABI differences between SH3 and SH4 remain)? (glibc doesn't
handle any sort of SH3 hard float at present; most things to do with
floating-point registers, exceptions and rounding modes are in sh4 sysdeps
Joseph S. Myers