mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: mips fp32/fpxx/fp64 issues, r6 sjlj broken
Date: Fri, 27 Sep 2019 13:10:28 +0200	[thread overview]
Message-ID: <20190927111027.GN22009@port70.net> (raw)
In-Reply-To: <20190927003821.GE9017@brightrain.aerifal.cx>

* Rich Felker <dalias@libc.org> [2019-09-26 20:38:21 -0400]:
> On Thu, Sep 26, 2019 at 07:23:50PM -0400, Rich Felker wrote:
> > On Thu, Sep 26, 2019 at 06:45:21PM -0400, Rich Felker wrote:
> > > Also, mipsr6 (the new mips-family ISA that's not compatible with
> > > previous mips) always uses the 64-bit register mode. We presently do
> > > not have setjmp/longjmp code that works with this case at all
> > > (existing code will wrongly save low 32-bits of 2 registers instead of
> > > single whole double register); somehow nobody has noticed that this is
> > > broken. Making this conditional on __mips_isa_rev >= 6 should not be
> > > hard.
> > 
> > Attached patch should work, but maybe isn't the best thing to do. I
> > think using sdc1/ldc1 and just even indices like on r6 would also be
> > valid for pre-r6 mips using fp32 or fpxx abi; with FR=0, it would
> > save/restore the pair of 32-bit registers, and with FR=1, fp32 code
> > could not be running anyway, and fpxx code should work fine. However,
> > mips I lacks the ldc1/stc1 instructions, so at the very least we'd
> > need to leave the old form in place for mips I. Or maybe use the s.d
> > and l.d mnemonics that automatically assemble to the right choice
> > based on the isa level...
> 
> Two new versions of the patch. I think I prefer the last one.
> 
> l.d and s.d expand to pairs of lwc1 and swc1 on mips1, and otherwise
> expand to ldc1 and sdc1. ldc1 and sdc1 in turn behave just like pairs
> of lwc1 and swc1 when FR=0, but additionally match the fpxx ABI when
> FR=1.

so a mips1 libc.so won't work on a system with FR=1?
but a mips2 libc.so works with both FR=1 and FR=0?

if mipsisa32r6 uses FR=1 and normal 32bit mips uses FR=0
then this sounds like an issue.

> 
> With this the r6 and clang issues should be fixed.
> 
> Rich

> diff --git a/src/setjmp/mips/longjmp.S b/src/setjmp/mips/longjmp.S
> index fdb6c95d..4d39c88e 100644
> --- a/src/setjmp/mips/longjmp.S
> +++ b/src/setjmp/mips/longjmp.S
> @@ -12,6 +12,14 @@ longjmp:
>  	addu    $2, $2, 1
>  1:
>  #ifndef __mips_soft_float
> +#if __mips >= 2
> +	ldc1	$20, 56($4)
> +	ldc1	$22, 64($4)
> +	ldc1	$24, 72($4)
> +	ldc1	$26, 80($4)
> +	ldc1	$28, 88($4)
> +	ldc1	$30, 96($4)
> +#else
>  	lwc1    $20, 56($4)
>  	lwc1    $21, 60($4)
>  	lwc1    $22, 64($4)
> @@ -24,6 +32,7 @@ longjmp:
>  	lwc1    $29, 92($4)
>  	lwc1    $30, 96($4)
>  	lwc1    $31, 100($4)
> +#endif
>  #endif
>  	lw      $ra,  0($4)
>  	lw      $sp,  4($4)
> diff --git a/src/setjmp/mips/setjmp.S b/src/setjmp/mips/setjmp.S
> index 501d5264..5d385f91 100644
> --- a/src/setjmp/mips/setjmp.S
> +++ b/src/setjmp/mips/setjmp.S
> @@ -22,6 +22,14 @@ setjmp:
>  	sw      $30, 40($4)
>  	sw      $28, 44($4)
>  #ifndef __mips_soft_float
> +#if __mips >= 2
> +	sdc1	$20, 56($4)
> +	sdc1	$22, 64($4)
> +	sdc1	$24, 72($4)
> +	sdc1	$26, 80($4)
> +	sdc1	$28, 88($4)
> +	sdc1	$30, 96($4)
> +#else
>  	swc1    $20, 56($4)
>  	swc1    $21, 60($4)
>  	swc1    $22, 64($4)
> @@ -34,6 +42,7 @@ setjmp:
>  	swc1    $29, 92($4)
>  	swc1    $30, 96($4)
>  	swc1    $31, 100($4)
> +#endif
>  #endif
>  	jr      $ra
>  	li      $2, 0

> diff --git a/src/setjmp/mips/longjmp.S b/src/setjmp/mips/longjmp.S
> index fdb6c95d..ecf40855 100644
> --- a/src/setjmp/mips/longjmp.S
> +++ b/src/setjmp/mips/longjmp.S
> @@ -12,18 +12,12 @@ longjmp:
>  	addu    $2, $2, 1
>  1:
>  #ifndef __mips_soft_float
> -	lwc1    $20, 56($4)
> -	lwc1    $21, 60($4)
> -	lwc1    $22, 64($4)
> -	lwc1    $23, 68($4)
> -	lwc1    $24, 72($4)
> -	lwc1    $25, 76($4)
> -	lwc1    $26, 80($4)
> -	lwc1    $27, 84($4)
> -	lwc1    $28, 88($4)
> -	lwc1    $29, 92($4)
> -	lwc1    $30, 96($4)
> -	lwc1    $31, 100($4)
> +	l.d     $f20, 56($4)
> +	l.d     $f22, 64($4)
> +	l.d     $f24, 72($4)
> +	l.d     $f26, 80($4)
> +	l.d     $f28, 88($4)
> +	l.d     $f30, 96($4)
>  #endif
>  	lw      $ra,  0($4)
>  	lw      $sp,  4($4)
> diff --git a/src/setjmp/mips/setjmp.S b/src/setjmp/mips/setjmp.S
> index 501d5264..7ae8832d 100644
> --- a/src/setjmp/mips/setjmp.S
> +++ b/src/setjmp/mips/setjmp.S
> @@ -22,18 +22,12 @@ setjmp:
>  	sw      $30, 40($4)
>  	sw      $28, 44($4)
>  #ifndef __mips_soft_float
> -	swc1    $20, 56($4)
> -	swc1    $21, 60($4)
> -	swc1    $22, 64($4)
> -	swc1    $23, 68($4)
> -	swc1    $24, 72($4)
> -	swc1    $25, 76($4)
> -	swc1    $26, 80($4)
> -	swc1    $27, 84($4)
> -	swc1    $28, 88($4)
> -	swc1    $29, 92($4)
> -	swc1    $30, 96($4)
> -	swc1    $31, 100($4)
> +	s.d     $f20, 56($4)
> +	s.d     $f22, 64($4)
> +	s.d     $f24, 72($4)
> +	s.d     $f26, 80($4)
> +	s.d     $f28, 88($4)
> +	s.d     $f30, 96($4)
>  #endif
>  	jr      $ra
>  	li      $2, 0



  reply	other threads:[~2019-09-27 11:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 22:45 Rich Felker
2019-09-26 23:23 ` Rich Felker
2019-09-27  0:38   ` Rich Felker
2019-09-27 11:10     ` Szabolcs Nagy [this message]
2019-09-27 11:52       ` Rich Felker
2019-09-27 11:55         ` Szabolcs Nagy
2019-09-27 14:44           ` 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=20190927111027.GN22009@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    /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).