From: Alistair Francis <alistair23@gmail.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Alistair Francis via Libc-alpha <libc-alpha@sourceware.org>,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH 1/2] rsciv: Consolidate the libm-test-ulps
Date: Fri, 4 Sep 2020 13:39:23 -0700 [thread overview]
Message-ID: <CAKmqyKMfpdf1T8m4C5LjaqOtbZQwEDEkPf0Wo+uh9nywnF3O7w@mail.gmail.com> (raw)
In-Reply-To: <87h7sdgue8.fsf@mid.deneb.enyo.de>
On Fri, Sep 4, 2020 at 1:27 PM Florian Weimer <fw@deneb.enyo.de> wrote:
>
> * Alistair Francis via Libc-alpha:
>
> > Both RV32 and RV64 have the same libm-test-ulps, so consolidate them
> > into a single file.
>
> Typo in the commit subject.
Thanks, fixed.
>
> Is it likely that there will be future divergence?
I don't think so. When I was upstreaming the 32-bit port Joseph
mentioned that they should be the same.
Alistair
prev parent reply other threads:[~2020-09-04 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 19:45 Alistair Francis
2020-09-04 19:45 ` [PATCH 2/2] riscv: Remove RV32 floating point functions Alistair Francis
2020-09-04 20:27 ` [PATCH 1/2] rsciv: Consolidate the libm-test-ulps Florian Weimer
2020-09-04 20:39 ` Alistair Francis [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=CAKmqyKMfpdf1T8m4C5LjaqOtbZQwEDEkPf0Wo+uh9nywnF3O7w@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.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).