From: Marek Polacek <polacek@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c-family: Add <time.h> names to diagnostics for known headers
Date: Tue, 5 Jul 2022 10:58:40 -0400 [thread overview]
Message-ID: <YsRRoPXs1qGLywyQ@redhat.com> (raw)
In-Reply-To: <CACb0b4k4+PRA1VMRFczPhsjY3DpYjOHsyidh-d8OwtUgGYtX8g@mail.gmail.com>
On Mon, Jul 04, 2022 at 05:25:42PM +0100, Jonathan Wakely wrote:
> On Thu, 30 Jun 2022 at 16:15, Marek Polacek wrote:
> >
> > On Thu, Jun 30, 2022 at 04:11:42PM +0100, Jonathan Wakely via Gcc-patches wrote:
> > > I recently changed <string> to no longer include an unnecessary header,
> > > which meant it no longer includes <pthread.h>, which means it no longer
> > > includes <time.h>. This resulted in some build failures:
> > > https://issues.apache.org/jira/browse/LUCENE-10630
> > > https://github.com/openSUSE/libzypp/pull/405
> > >
> > > And that revealed that we don't suggest the right header for those
> > > functions. Fixed like so.
> > >
> > > Tested x86_64-linux. OK for trunk?
> >
> > Ok, thanks.
>
> OK for gcc-12 too? I already backported the include streamlining for
> <string> that causes several packages to get errors for missing
> <ctime>, so it makes sense to also backport these improved
> diagnostics.
Since the patch isn't adding any new diagnostics that previously wasn't
there, I think it's OK as well, thanks.
Marek
prev parent reply other threads:[~2022-07-05 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 15:11 Jonathan Wakely
2022-06-30 15:15 ` Marek Polacek
2022-07-04 16:25 ` Jonathan Wakely
2022-07-05 14:58 ` Marek Polacek [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=YsRRoPXs1qGLywyQ@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@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).