public inbox for
 help / color / mirror / Atom feed
From: Doug Gilmore <>
To: Joseph S.Myers <>, <>
Subject: Re: [Patch, mips]: Add support for FR=1/o32. Update implemention of setjmp/longjmp
Date: Wed, 04 Dec 2013 02:45:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 11/26/2013 08:21 AM, Joseph S.Myers wrote:
Hi Joseph,

Sorry for the delay in responding, there were issues with the
*context routines I wanted to understand more fully, thus the delay.
> On Tue, 26 Nov 2013, Matheus Almeida wrote:
>> 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.
Good point, we will attend to that.

> I don't recall a response to 
> <>, and don't see
> one in the binutils list archives.  I believe that just like the NaN 
> changes, this needs to be considered as an incompatible ABI variant, with 
> ELF header checks in the dynamic linker to ensure that all loaded objects 
> are compatible (whether or not you also define new dynamic linker names 
> for one or both of o32/-mfp64/legacy-NaN and o32/-mfp64/NaN-2008) - 
> incompatibilities should be detected by the dynamic linker, not "need to 
> be recompiled".  I suggest looking at Maciej's NaN changes as a model.
Yes, this is definitely something we need to attend to.

> Also as suggested in that message to the binutils list, I think *context 
> functions need updating
An important motivation for adding -mfp64 support is to efficiently
support the new MSA ISA, which requires the register file to operate
in -mfp64 mode when MSA instructions are executed.  Since the
definition of ucontext_t is basically the kernel's struct sigcontext,
with possibly with some massaging some of the types used in the
definition, our preference is to wait in adding this functionality
once MSA context switching support is added to the Linux kernel.

If worse comes to worse we may have to live with the *context routines
not being supported properly, just as they are on X86_64 in AVX mode.
> as well as setjmp/longjmp, and there should be an 
> ABI supplement document explaining o32 function call and return for 
> -mfp64.
Will do.

> What's the kernel version with support for this feature (that 
> is, the kernel that checks the ELF header flag and ensures the FPU is 
> correctly set up for the process)?  As with NaN-2008, arch_minimum_kernel 
> should be set to the appropriate kernel version, or 10.0.0 until the 
> relevant support is in the tree.

In your follow-up message you wrote:
> Sorry, I see your "need to be recompiled" was about old -mfp64 binaries, 
> which indeed we don't need to care about.
Is the kernel version check still a concern given that currently there
is no ToT kernel support for -mfp64?  We just need to add the checks to
ensure the dynamic linker will only map compatible shared objects.  Right?



  parent reply	other threads:[~2013-12-04  2:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 11:34 Matheus Almeida
2013-11-26 16:25 ` Joseph S. Myers
2013-11-30  8:03   ` Joseph S. Myers
2013-12-04  2:45   ` Doug Gilmore [this message]
2013-12-04 14:56     ` Joseph S. Myers

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).