From: Stefan Liebler <stli@linux.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] Don't pass NULL pointer to error [BZ #24556]
Date: Tue, 18 Jun 2019 09:10:35 +0200 [thread overview]
Message-ID: <33741881-94c0-eef0-5c76-4c72c8bf394e@linux.ibm.com> (raw)
In-Reply-To: <CAMe9rOogEhm1OFDB9jPOK7cZ1CNTLkGHcBYFz01xfhY_0gUG7A@mail.gmail.com>
On 6/17/19 9:32 PM, H.J. Lu wrote:
> 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?
>
Sorry. I've just recognized this thread.
I've already posted a patch which also fixes "make bench" with gcc 9:
"[PATCH] Fix gcc 9 build errors for make xcheck."
https://www.sourceware.org/ml/libc-alpha/2019-06/msg00374.html
Bye
Stefan
prev parent reply other threads:[~2019-06-18 7:10 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
2019-06-18 7:10 ` Stefan Liebler [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=33741881-94c0-eef0-5c76-4c72c8bf394e@linux.ibm.com \
--to=stli@linux.ibm.com \
--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).