public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH 1/4] libstdc++: Import parts of the Ryu library
Date: Thu, 17 Dec 2020 14:34:42 +0000	[thread overview]
Message-ID: <20201217143442.GB2309743@redhat.com> (raw)
In-Reply-To: <20200714194146.3978209-1-ppalka@redhat.com>

On 14/07/20 15:41 -0400, Patrick Palka via Libstdc++ wrote:
>This imports the source files from the Ryu library that define
>d2s_buffered_n, f2s_buffered_n, d2fixed_buffered_n and d2exp_buffered_n
>and generic_binary_to_decimal, which we're going to need as part of our
>std::to_chars implementation.
>
>libstdc++-v3/ChangeLog:
>
>	* src/c++17/ryu/MERGE: New file.
>	* src/c++17/ryu/common.h, src/c++17/ryu/d2fixed.c,
>	src/c++17/ryu/d2fixed_full_table.h, src/c++17/ryu/d2s.c,
>	src/c++17/ryu/d2s_full_table.h, src/c++17/ryu/d2s_intrinsics.h,
>	src/c++17/ryu/digit_table.h, src/c++17/ryu/f2s.c,
>	src/c++17/ryu/f2s_instrinsics.h,
>	src/c++17/ryu/generic_128.c, src/c++17/ryu/generic_128.h,
>	src/c++17/ryu/ryu_generic_128.h: Import these files from the
>	Ryu library.


OK for trunk.



      parent reply	other threads:[~2020-12-17 14:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 19:41 Patrick Palka
2020-07-14 19:41 ` [PATCH 2/4] libstdc++: Apply modifications to our local copy of Ryu Patrick Palka
2020-07-15 18:12   ` Patrick Palka
2020-12-17 14:35     ` Jonathan Wakely
2020-07-14 19:41 ` [PATCH 3/4] libstdc++: Add floating-point std::to_chars implementation Patrick Palka
2020-07-15 18:21   ` Patrick Palka
2020-07-17  4:23     ` Patrick Palka
2020-07-17 16:24       ` Patrick Palka
2020-07-20  3:37         ` Patrick Palka
2020-07-20 12:31           ` Jonathan Wakely
2020-07-20 12:53             ` Patrick Palka
2020-07-20 14:13               ` Jonathan Wakely
2020-07-20 14:46                 ` Patrick Palka
2020-07-22 15:56                   ` Patrick Palka
2020-08-19 21:57                     ` Patrick Palka
2020-12-17 14:32                       ` Jonathan Wakely
2020-12-18  4:13                         ` Patrick Palka
2020-12-18 13:24                           ` Christophe Lyon
2020-12-18 14:58                             ` Jonathan Wakely
2020-12-18 15:00                             ` Patrick Palka
2020-12-18 16:52                               ` Christophe Lyon
2020-12-18 17:03                                 ` Patrick Palka
2020-12-18 18:28                                   ` Christophe Lyon
2020-12-20 21:44                           ` Maciej W. Rozycki
2020-12-21 17:06                             ` Patrick Palka
2020-12-21 23:09                               ` Maciej W. Rozycki
2020-07-14 19:41 ` [PATCH 4/4] libstdc++: Import MSVC floating-point std::to_chars testcases Patrick Palka
2020-07-14 19:49   ` Patrick Palka
2020-12-17 14:37   ` Jonathan Wakely
2020-07-14 19:46 ` [PATCH 1/4] libstdc++: Import parts of the Ryu library Patrick Palka
2020-07-25 11:44 ` Václav Haisman
2020-07-26 13:09   ` Patrick Palka
2020-12-17 14:34 ` Jonathan Wakely [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=20201217143442.GB2309743@redhat.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ppalka@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).