public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Matheus Almeida <Matheus.Almeida@imgtec.com>
To: "libc-ports@sourceware.org" <libc-ports@sourceware.org>
Cc: Doug Gilmore <Doug.Gilmore@imgtec.com>
Subject: RE: [Patch, mips]: Add support for FR=1/o32. Update implementation of setjmp/longjmp
Date: Tue, 26 Nov 2013 14:52:00 -0000	[thread overview]
Message-ID: <D27A34061895C147B6015779E8B217303D498467@KLMAIL01.kl.imgtec.org> (raw)

Fixed typo in subject line.

-----Original Message-----
From: Matheus Almeida 
Sent: 26 November 2013 11:14
To: libc-ports@sourceware.org
Cc: Doug Gilmore
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.

Regards,
Matheus

Matheus Almeida
MIPS processor IP
www.imgtec.com


                 reply	other threads:[~2013-11-26 11:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=D27A34061895C147B6015779E8B217303D498467@KLMAIL01.kl.imgtec.org \
    --to=matheus.almeida@imgtec.com \
    --cc=Doug.Gilmore@imgtec.com \
    --cc=libc-ports@sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).