From: Dan Malek <dan@embeddededge.com>
To: Shie Erlich <shie_e@elbit.co.il>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 64 bit memory access - again ...
Date: Wed, 05 Dec 2001 12:16:41 -0500 [thread overview]
Message-ID: <3C0E5679.4060407@embeddededge.com> (raw)
In-Reply-To: 937610FE9B70D511B3E700508B8B65770E53DC@MAIL1
Shie Erlich wrote:
> the FPU solution does work, however (and thanks for the pointers) - but if
> my
> function saves the fpu registers and restores them, do i really need to
> force
> the kernel to context switch the fpu ?
You have to be careful that moving the bits in/out of the FP register
doesn't have other side effects in FP status or condition codes. Always
saving/restoring the context will guarantee the application doesn't see
these side effects, but you can experiment if you wish.
Good Luck.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-05 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 9:25 64 bit memory access - again Shie Erlich
2001-12-05 17:16 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-03 11:14 Shie Erlich
2001-12-03 17:01 ` Dan Malek
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=3C0E5679.4060407@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=shie_e@elbit.co.il \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.