public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jun Nakajima <jun@sco.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Using f6-f11 floating-point registers
Date: Wed, 28 Jun 2000 13:57:10 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205184@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205181@msgid-missing>

Well, I was just wondering because your (with Don) viewgraphs "IA-64
Linux Kernel Internals" (on the IA-64 Linux Web home page) says (p. 9)
"considering a change to only provide f6-f11 to the compiler for integer
multiply and divide", and I wanted to know how serious you were about
it.

David Mosberger wrote:
> 
> >>>>> On Tue, 27 Jun 2000 18:02:09 -0400, Jun Nakajima <jun@sco.com> said:
> 
>   Jun> At this point, the kernel is using more than f6-f11
>   Jun> floating-point registers (using -mfixed-rangeñ0-f15,f32-f127,
>   Jun> i.e. those are *not* available to the kernel, but the others,
>   Jun> like f16-f31 are).
> 
> If the compiler or someone writing assembly code thinks it's
> beneficial to use a preserved fp register, we should let them use it.
> Of course, they'll have to explicitly save/restore the register before
> using it, but there may well be cases where this is beneficial, so we
> shouldn't prevent it for no good reason.
> 
>   Jun> When do we support the reduced FP model (EL_IA_64_REDUCEFP),
>   Jun> where only f6-f11 are used by the kernel?
> 
> For the record, I have no plans to adopt the REDUCEFP model.  I want
> to reserve the right for kernel developers to tweak the kernel
> register usage without having to talk to a standards body.  Sorry.
> 
>         --david

-- 
Jun U Nakajima
Core OS Development
SCO/Murray Hill, NJ



      parent reply	other threads:[~2000-06-28 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-27 22:02 [Linux-ia64] Using f6-f11 floating-point registers Jun Nakajima
2000-06-27 22:44 ` James Wilson
2000-06-28  0:20 ` David Mosberger
2000-06-28 13:57 ` Jun Nakajima [this message]

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=marc-linux-ia64-105590678205184@msgid-missing \
    --to=jun@sco.com \
    --cc=linux-ia64@vger.kernel.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