From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][_GLIBCXX_INLINE_VERSION] Fix test dg-prune-output
Date: Thu, 15 Sep 2022 15:12:28 +0100 [thread overview]
Message-ID: <CACb0b4kK650zv1m9O-rZ6UR127PqPyXwiYNFDfRk4mvbYg9u6Q@mail.gmail.com> (raw)
In-Reply-To: <99765d4f-2ac6-5877-69b6-1bd8684c20ff@gmail.com>
On Wed, 14 Sept 2022 at 18:26, François Dumont via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> libstdc++: [_GLIBCXX_INLINE_VERSION] Fix test dg-prune-output
>
> libstdc++-v3/ChangeLog:
>
> *
> testsuite/20_util/is_complete_or_unbounded/memoization_neg.cc: Adapt
Please put the "Adapt" on the next line. The file path is already
longer than the maximum line for a ChangeLog :-(
OK with that adjustment, thanks!
> dg-prune-output to
> _GLIBCXX_INLINE_VERSION mode.
>
>
> With this patch all tests are Ok in _GLIBCXX_INLINE_VERSION mode (at the
> time I'm writing this).
>
> Ok to commit ?
>
> François
prev parent reply other threads:[~2022-09-15 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 17:26 François Dumont
2022-09-15 14:12 ` Jonathan Wakely [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=CACb0b4kK650zv1m9O-rZ6UR127PqPyXwiYNFDfRk4mvbYg9u6Q@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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).