From: "Frank Ch. Eigler" <fche@redhat.com>
To: Ben Elliston <bje@redhat.com>
Cc: sid@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: [RFA] New SUBWORD* functions for SID CPUs
Date: Thu, 31 Jan 2002 04:35:00 -0000 [thread overview]
Message-ID: <20020131073546.E22071@redhat.com> (raw)
In-Reply-To: <15449.14439.853756.277945@scooby.brisbane.redhat.com>; from bje@redhat.com on Thu, Jan 31, 2002 at 11:28:23PM +1100
[-- Attachment #1: Type: text/plain, Size: 495 bytes --]
Hi -
On Thu, Jan 31, 2002 at 11:28:23PM +1100, Ben Elliston wrote:
> The following patch adds a number of new mode conversion functions for
> SID CPU components. Some, such as SUBWORDSISF, simply perform
> coercion between modes. Okay to commit?
Of course -- such library build-outs don't need elaborate approvals.
Are you sure though that the SF<->SI routines are meant to consist
of plain coercion (as in truncate-to-int), instead of the equivalent
to
* (int *) (& a.float.var)
?
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-01-31 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 4:28 Ben Elliston
2002-01-31 4:35 ` Frank Ch. Eigler [this message]
2002-01-31 17:04 ` Ben Elliston
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=20020131073546.E22071@redhat.com \
--to=fche@redhat.com \
--cc=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=sid@sources.redhat.com \
/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).