unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Gabriel F. T. Gomes" <gabriel@inconstante.net.br>
To: <libc-alpha@sourceware.org>
Subject: Ping. Re: [PATCH 0/6] IEEE long double printf and friends for powerpc64le
Date: Mon, 2 Sep 2019 11:15:13 -0300	[thread overview]
Message-ID: <20190902111513.515d02ad@tereshkova> (raw)
In-Reply-To: <20190809183154.32605-1-gabriel@inconstante.net.br>

Any comments on these patches?

I believe I have addressed all the comments in previous submissions.

On Fri, 09 Aug 2019, Gabriel F. T. Gomes wrote:

>From: "Gabriel F. T. Gomes" <gabrielftg@linux.ibm.com>
>
>A long time ago [1], I sent a patch set with the initial implementations
>of many string to/from IEEE long double conversion routines for
>powerpc64le.  The patch set depended on other, at the time unapplied,
>patch sets [2,3], which are now all integrated into master.  Even though
>this dependency existed, I got a lot of feedback (thanks, btw), which I
>tried to address for this new round.
>
>In this thread, I only included printf and friends functions, which
>helps reduce the size of the patch set and maybe ease review. :)
>
>As with previous submissions, these changes can only be tested once all
>other functions have actually been integrated (because the function
>redirections in our installed headers are macroized and work for all
>long double routines).  So, in order to test it, I use a more complete
>branch, which I made available at:
>https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/gabriel/powerpc-ieee128-printscan
>
>[1] https://sourceware.org/ml/libc-alpha/2018-06/msg00652.html
>[2] https://sourceware.org/ml/libc-alpha/2018-10/msg00612.html
>[3] https://sourceware.org/ml/libc-alpha/2019-02/msg00582.html
>
>Gabriel F. T. Gomes (6):
>  ldbl-128ibm-compat: Add regular character printing functions
>  ldbl-128ibm-compat: Add wide character printing functions
>  ldbl-128ibm-compat: Add regular character, fortified printing
>    functions
>  ldbl-128ibm-compat: Add wide character, fortified printing functions
>  ldbl-128ibm-compat: Test double values
>  ldbl-128ibm-compat: Test positional arguments

      parent reply	other threads:[~2019-09-02 14:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 18:31 [PATCH 0/6] IEEE long double printf and friends for powerpc64le Gabriel F. T. Gomes
2019-08-09 18:31 ` [PATCH 1/6] ldbl-128ibm-compat: Add regular character printing functions Gabriel F. T. Gomes
2019-08-14 11:46   ` Florian Weimer
2019-08-15 18:30     ` Gabriel F. T. Gomes
2019-09-02 14:03       ` Gabriel F. T. Gomes
2019-09-02 14:28         ` Florian Weimer
2019-09-02 15:11           ` Gabriel F. T. Gomes
2019-08-09 18:31 ` [PATCH 2/6] ldbl-128ibm-compat: Add wide " Gabriel F. T. Gomes
2019-08-09 18:31 ` [PATCH 3/6] ldbl-128ibm-compat: Add regular character, fortified " Gabriel F. T. Gomes
2019-08-09 18:31 ` [PATCH 4/6] ldbl-128ibm-compat: Add wide " Gabriel F. T. Gomes
2019-08-09 18:31 ` [PATCH 5/6] ldbl-128ibm-compat: Test double values Gabriel F. T. Gomes
2019-08-09 18:31 ` [PATCH 6/6] ldbl-128ibm-compat: Test positional arguments Gabriel F. T. Gomes
2019-09-02 14:15 ` Gabriel F. T. Gomes [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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190902111513.515d02ad@tereshkova \
    --to=gabriel@inconstante.net.br \
    --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).