From: Philippe Vachon <philippe@cowpig.ca>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
"Maciej W. Rozycki" <macro@codesourcery.com>,
linux-mips@linux-mips.org, libc-ports@sourceware.org
Subject: Re: [PATCH, RFC] MIPS: Implement the getcontext API
Date: Tue, 28 Apr 2009 15:21:20 -0400 [thread overview]
Message-ID: <20090428192120.GA8066@cowpig.ca> (raw)
In-Reply-To: <20090428191750.GZ4902@hall.aurel32.net>
Hi,
On Tue, Apr 28, 2009 at 09:17:50PM +0200, Aurelien Jarno wrote:
> Note that this code does not compile on mips64, I get the following
> error from binutils (2.19.1):
> ../ports/sysdeps/unix/sysv/linux/mips/getcontext.S: Assembler messages:
> ../ports/sysdeps/unix/sysv/linux/mips/getcontext.S:102: Error: illegal operands `s.d fs6,(30*8+296)($4)'
> ../ports/sysdeps/unix/sysv/linux/mips/getcontext.S:103: Error: illegal operands `s.d fs7,(31*8+296)($4)'
>
> The corresponding code lines are:
>
> 98 s.d fs2, (26 * SZREG + MCONTEXT_FPREGS)(a0)
> 99 s.d fs3, (27 * SZREG + MCONTEXT_FPREGS)(a0)
> 100 s.d fs4, (28 * SZREG + MCONTEXT_FPREGS)(a0)
> 101 s.d fs5, (29 * SZREG + MCONTEXT_FPREGS)(a0)
> 102 s.d fs6, (30 * SZREG + MCONTEXT_FPREGS)(a0)
> 103 s.d fs7, (31 * SZREG + MCONTEXT_FPREGS)(a0)
>
You're missing one of the patches in the series (the additional changes
to the floating point register names). Once you apply that, you should
be good to go.
Cheers,
Phil
next prev parent reply other threads:[~2009-04-28 19:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 0:12 [PATCH, RFC] MIPS: Implement the getcontext API Maciej W. Rozycki
2009-03-03 16:56 ` David Daney
2009-03-04 8:19 ` Brian Foster
2009-03-04 12:17 ` Daniel Jacobowitz
2009-03-04 16:36 ` David Daney
2009-04-02 13:29 ` Ralf Baechle
2009-04-02 20:06 ` Daniel Jacobowitz
2009-03-04 15:44 ` Ralf Baechle
2009-03-04 22:25 ` David VomLehn (dvomlehn)
2009-03-04 22:25 ` David VomLehn (dvomlehn)
2009-03-04 22:34 ` David Daney
2009-03-05 7:58 ` MIPS RI/XI & trampolines [was:- [PATCH, RFC] MIPS: Implement the getcontext API ] Brian Foster
2009-03-05 17:01 ` David Daney
2009-04-02 13:38 ` [PATCH, RFC] MIPS: Implement the getcontext API Ralf Baechle
2009-04-16 3:46 ` Markus Gothe
2009-04-17 5:53 ` Ralf Baechle
2009-03-05 15:34 ` Maciej W. Rozycki
2009-03-05 16:58 ` David Daney
2009-03-05 18:23 ` David VomLehn (dvomlehn)
2009-03-05 18:23 ` David VomLehn (dvomlehn)
2009-03-05 21:36 ` Ralf Baechle
2009-03-05 21:39 ` Roland McGrath
2009-03-05 21:53 ` Joseph S. Myers
2009-03-05 22:08 ` David VomLehn (dvomlehn)
2009-03-05 22:08 ` David VomLehn (dvomlehn)
2009-04-02 13:19 ` Ralf Baechle
2009-04-15 20:19 ` Joseph S. Myers
2009-04-15 21:37 ` David Daney
2009-04-18 12:38 ` Ralf Baechle
2009-04-18 17:32 ` Joseph S. Myers
2009-04-20 19:57 ` Maciej W. Rozycki
2009-04-28 19:17 ` Aurelien Jarno
2009-04-28 19:21 ` Philippe Vachon [this message]
2009-04-28 20:19 ` Maciej W. Rozycki
2009-04-28 20:53 ` Aurelien Jarno
2009-04-28 21:47 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2009-04-05 18:57 Graziano Sorbaioli
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=20090428192120.GA8066@cowpig.ca \
--to=philippe@cowpig.ca \
--cc=aurelien@aurel32.net \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@codesourcery.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox