From: "H.J. Lu" <hjl.tools@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Martin Sebor <msebor@gmail.com>,
Florian Weimer <fweimer@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
msebor@redhat.com
Subject: Re: [PATCH] Don't pass NULL pointer to error [BZ #24556]
Date: Mon, 17 Jun 2019 12:32:33 -0700 [thread overview]
Message-ID: <CAMe9rOogEhm1OFDB9jPOK7cZ1CNTLkGHcBYFz01xfhY_0gUG7A@mail.gmail.com> (raw)
In-Reply-To: <72f51389-2273-cce4-3997-5c825bf12c33@cs.ucla.edu>
On Thu, May 23, 2019 at 12:35 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> On 5/23/19 9:21 AM, Martin Sebor wrote:
> > I'd rather discourage
> > relying on the Glibc printf extension than remove the transformations
> > or suppress the warning.
>
> I agree that this is a good way to go, as we can't keep fighting
> compilers forever. I wrote a patch implementing this suggestion and
> filed a bug report proposing it here:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=24616
>
GCC 9 can't build bench today. What should we do?
--
H.J.
next prev parent reply other threads:[~2019-06-17 19:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 22:40 [PATCH] Don't pass NULL pointer to error [BZ #24556] H.J. Lu
2019-05-23 7:02 ` Florian Weimer
2019-05-23 14:57 ` H.J. Lu
2019-05-23 15:20 ` Florian Weimer
2019-05-23 15:28 ` H.J. Lu
2019-05-23 15:41 ` Florian Weimer
2019-05-23 16:21 ` Martin Sebor
2019-05-23 19:35 ` Paul Eggert
2019-06-17 19:32 ` H.J. Lu [this message]
2019-06-18 7:10 ` Stefan Liebler
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=CAMe9rOogEhm1OFDB9jPOK7cZ1CNTLkGHcBYFz01xfhY_0gUG7A@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=msebor@gmail.com \
--cc=msebor@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).