From: Stafford Horne <shorne@gmail.com>
To: cgen@sourceware.org
Cc: Openrisc <openrisc@lists.librecores.org>,
Stafford Horne <shorne@gmail.com>
Subject: [PATCH 0/2] CGEN unordered fpu compares + fixes
Date: Sat, 01 Jun 2019 07:26:00 -0000 [thread overview]
Message-ID: <20190601072629.4070-1-shorne@gmail.com> (raw)
Hello,
As I am working on openrisc which uses cgen in binutils I have needed to make
these changes.
The Unordered compares is needed for FPU unordered (NaN detecting) comparisons.
These have been implemented and tested in OpenRISC (both simulation and
assembler (running on FPGA hardware)).
The gen-doc changes come from me noticing the docs [0] on the cgen website are
very much out of date.
Does anyone know the process to get the regenerated docs posted? I think they
are beneficial and with some more updates they could be really good.
[0] https://sourceware.org/cgen/gen-doc/
Stafford Horne (2):
cgen: Add unordered compare operation
gen-doc: Updates for latest cpu definitions
gen-all-doc | 46 ++++++++++++++++++++++++++++++++--------------
html.scm | 2 +-
rtl-c.scm | 4 ++++
rtx-funcs.scm | 7 +++++++
4 files changed, 44 insertions(+), 15 deletions(-)
mode change 100644 => 100755 gen-all-doc
--
2.21.0
next reply other threads:[~2019-06-01 7:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 7:26 Stafford Horne [this message]
2019-06-01 7:26 ` [PATCH 1/2] cgen: Add unordered compare operation Stafford Horne
2019-06-01 7:26 ` [PATCH 2/2] gen-doc: Updates for latest cpu definitions Stafford Horne
2019-06-12 13:14 ` [PATCH 0/2] CGEN unordered fpu compares + fixes Stafford Horne
2019-06-12 14:36 ` Jose E. Marchesi
2019-06-12 15:04 ` Frank Ch. Eigler
2019-06-12 20:53 ` Stafford Horne
2019-06-12 21:54 ` Frank Ch. Eigler
2019-06-13 8:51 ` Jose E. Marchesi
2019-06-13 12:23 ` Stafford Horne
2019-06-13 15:02 ` Jose E. Marchesi
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=20190601072629.4070-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=cgen@sourceware.org \
--cc=openrisc@lists.librecores.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 read-only IMAP folder(s) and NNTP newsgroup(s).