From: Letu Ren <fantasquex@gmail.com>
To: libc-alpha@sourceware.org
Cc: fweimer@redhat.com, joseph@codesourcery.com, schwab@suse.de
Subject: Re: [PATCH v5] stdlib/strfrom: Add copysign to fix NAN issue on riscv (BZ #29501)
Date: Fri, 21 Oct 2022 16:57:27 +0800 [thread overview]
Message-ID: <CAEUwDuBw7iBVbQvrGjV068jNp_L1Tm4OekSP-2dD2PwZaF5O=g@mail.gmail.com> (raw)
In-Reply-To: <CAEUwDuDcbkCazvB2Px=VarL1R74JZRfodL+jQg5X8B7TNdWORA@mail.gmail.com>
Ping! It has been two weeks since I sent this patch. I'm willing to
hear some suggestions and feedback :)
next prev parent reply other threads:[~2022-10-21 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 15:01 Letu Ren
2022-10-13 13:02 ` Letu Ren
2022-10-21 8:57 ` Letu Ren [this message]
2022-10-21 13:08 ` Adhemerval Zanella Netto
2022-10-21 15:01 ` Letu Ren
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='CAEUwDuBw7iBVbQvrGjV068jNp_L1Tm4OekSP-2dD2PwZaF5O=g@mail.gmail.com' \
--to=fantasquex@gmail.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).