This is the mail archive of the
mailing list for the newlib project.
Re: [Patch, mips]: Add support for FR=1/o32. Update implemention of setjmp/longjmp
- From: Jeff Johnston <jjohnstn at redhat dot com>
- To: Matheus Almeida <Matheus dot Almeida at imgtec dot com>
- Cc: newlib at sourceware dot org, Doug Gilmore <Doug dot Gilmore at imgtec dot com>
- Date: Tue, 26 Nov 2013 14:59:01 -0500 (EST)
- Subject: Re: [Patch, mips]: Add support for FR=1/o32. Update implemention of setjmp/longjmp
- Authentication-results: sourceware.org; auth=none
- References: <D27A34061895C147B6015779E8B217303D498430 at KLMAIL01 dot kl dot imgtec dot org>
Patch checked in. In the future, please add a ChangeLog entry so I don't have
to make one up for you.
-- Jeff J.
----- Original Message -----
From: "Matheus Almeida" <Matheus.Almeida@imgtec.com>
Cc: "Doug Gilmore" <Doug.Gilmore@imgtec.com>
Sent: Tuesday, November 26, 2013 6:30:04 AM
Subject: [Patch, mips]: Add support for FR=1/o32. Update implemention of setjmp/longjmp
Mips allow the width of FPU registers to be controlled by specifying the FR configuration bit:
FR=0 -> 32-bit FPU registers
FR=1 -> 64-bit FPU registers
This can be controlled by -mfp32/-mfp64 command line options.
This patch updates the definition of setjmp, longjmp and jmp_buf so that on a call to setjmp/longjmp, all the required floating-point callee-saved registers are properly saved/restored.
We are aware that updating the size of jmp_buf can potentially break existing applications but we expect the number of applications built with FR=1 mode to be very small, possibly zero. Nevertheless this should be clearly stated in the release notes that existing applications built with FR=1 (-mfp64) need to be recompiled in order to use new versions of the library.
MIPS processor IP