From: Joseph Myers <joseph@codesourcery.com>
To: "Gabriel F. T. Gomes" <gabriel@inconstante.eti.br>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH v4 3/5] ldbl-opt: Add err, errx, verr, verrx, warn, warnx, vwarn, and vwarnx (bug 23984)
Date: Thu, 28 Feb 2019 18:38:47 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1902281838180.20103@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20190221205706.12225-4-gabriel@inconstante.eti.br>
OK, although this is missing libnldbl_nonshared.a additions, and unlike in
patch 1 adding those would not require any further exports from libc.so.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-02-28 18:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 20:57 [PATCH v4 0/5] Add missing nldbl functions to libc Gabriel F. T. Gomes
2019-02-21 20:57 ` [PATCH v4 1/5] ldbl-opt: Add arpg_error and argp_failure (bug 23983) Gabriel F. T. Gomes
2019-02-28 18:35 ` Joseph Myers
2019-02-21 20:57 ` [PATCH v4 2/5] ldbl-opt: Reuse argp tests that print long double Gabriel F. T. Gomes
2019-02-28 18:36 ` Joseph Myers
2019-02-21 20:57 ` [PATCH v4 3/5] ldbl-opt: Add err, errx, verr, verrx, warn, warnx, vwarn, and vwarnx (bug 23984) Gabriel F. T. Gomes
2019-02-28 18:38 ` Joseph Myers [this message]
2019-02-21 20:57 ` [PATCH v4 4/5] ldbl-opt: Add error and error_at_line " Gabriel F. T. Gomes
2019-02-28 18:40 ` Joseph Myers
2019-02-21 20:57 ` [PATCH v4 5/5] ldbl-opt: Reuse test cases from misc/ that check long double Gabriel F. T. Gomes
2019-02-28 18:41 ` Joseph Myers
2019-02-28 14:02 ` Ping. Re: [PATCH v4 0/5] Add missing nldbl functions to libc Gabriel F. T. Gomes
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=alpine.DEB.2.21.1902281838180.20103@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gabriel@inconstante.eti.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).