From: Fredrik Noring <noring@nocrew.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Petar Jovanovic" <pjovanovic@wavecomp.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Jürgen Urban" <JuergenUrban@gmx.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 6/8] target/mips: Define the R5900 CPU
Date: Sun, 21 Oct 2018 14:34:23 +0200 [thread overview]
Message-ID: <20181021123423.GA2666@sx9> (raw)
In-Reply-To: <alpine.LFD.2.21.1809210020490.19067@eddie.linux-mips.org>
Hi Maciej,
> The C790 is a follow-up to the R5900. The R5900 has an FPU that is not
> compliant to the IEEE 754 standard for floating-point arithmetic. It
> doesn't implement exceptions, infinities, NaNs or denormals. It doesn't
> implement the the double format either, but that is really tangential,
> because the same was the case with the IDT R4650, which had a standard
> IEEE 754 FPU, but no double format either. Finally it has some anomalies
> in the FP instruction set; not all opcode encodings are standard.
Do you know where one might find a list of the nonstandard FP instructions?
The command
% grep 'FP_.*EE' binutils/opcodes/mips-opc.c
gives a list of candidates, I suppose?
Fredrik
next parent reply other threads:[~2018-10-21 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1537379317.git.noring@nocrew.org>
[not found] ` <b4a7f8e59ba8f6eaa03e7fe24690df7b39b17e8d.1537379317.git.noring@nocrew.org>
[not found] ` <f299b045-eac4-9dec-3999-627d9984141f@amsat.org>
[not found] ` <alpine.LFD.2.21.1809210020490.19067@eddie.linux-mips.org>
2018-10-21 12:34 ` Fredrik Noring [this message]
2018-10-21 15:21 ` [Qemu-devel] [PATCH v5 6/8] target/mips: Define the R5900 CPU Maciej W. Rozycki
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=20181021123423.GA2666@sx9 \
--to=noring@nocrew.org \
--cc=JuergenUrban@gmx.de \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=macro@linux-mips.org \
--cc=peter.maydell@linaro.org \
--cc=pjovanovic@wavecomp.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 NNTP newsgroup(s).