From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] Fix dg-prune-output
Date: Sun, 8 Aug 2021 21:54:09 +0100 [thread overview]
Message-ID: <CAH6eHdRprBmWOiop6jRfeovRBn1soxS7_y7yYm_=ZBNjqG-uYA@mail.gmail.com> (raw)
In-Reply-To: <bff2367d-5261-37f3-35cf-fc5c1a39020b@gmail.com>
On Sun, 8 Aug 2021, 20:26 François Dumont via Libstdc++, <
libstdc++@gcc.gnu.org> wrote:
> This is a trivial fix following a recent change on __glibcxx_assert.
>
> libstdc++: Fix dg-prune-output assertion message
>
> Since __glibcxx_assert changes in r6b42b5a the generated assertion
> message
> has changed.
>
Ah yes, thanks for fixing this.
> libstdc++-v3/ChangeLog:
>
> * testsuite/25_algorithms/copy/debug/constexpr_neg.cc:
> Replace 'failed_assertion'
> dg-prune-output reason with 'builtin_unreachable'.
> *
> testsuite/25_algorithms/copy_backward/debug/constexpr_neg.cc: Likewise.
> * testsuite/25_algorithms/equal/debug/constexpr_neg.cc:
> Likewise.
> *
> testsuite/25_algorithms/lower_bound/debug/constexpr_partitioned_neg.cc:
> Likewise.
> *
> testsuite/25_algorithms/lower_bound/debug/constexpr_partitioned_pred_neg.cc:
>
> Likewise.
> *
> testsuite/25_algorithms/lower_bound/debug/constexpr_valid_range_neg.cc:
> Likewise.
> *
> testsuite/25_algorithms/upper_bound/debug/constexpr_partitioned_neg.cc:
> Likewise.
> *
> testsuite/25_algorithms/upper_bound/debug/constexpr_partitioned_pred_neg.cc:
>
> Likewise.
> *
> testsuite/25_algorithms/upper_bound/debug/constexpr_valid_range_neg.cc:
> Likewise.
>
> François
>
>
prev parent reply other threads:[~2021-08-08 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 19:25 François Dumont
2021-08-08 20:54 ` 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='CAH6eHdRprBmWOiop6jRfeovRBn1soxS7_y7yYm_=ZBNjqG-uYA@mail.gmail.com' \
--to=jwakely.gcc@gmail.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).