public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "webrown.cpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107778] handle_contract_violation should reflect _GLIBCXX_VERBOSE
Date: Fri, 23 Dec 2022 00:54:21 +0000 [thread overview]
Message-ID: <bug-107778-4-GBlXb455ch@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107778-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107778
--- Comment #10 from W E Brown <webrown.cpp at gmail dot com> ---
> On Dec 22, 2022, at 6:51 PM, cvs-commit at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> wrote:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107778
>
> --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
> The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:
>
> https://gcc.gnu.org/g:8ec5fcb6fc79e5bcca23c3fecbaf09d4566cb1d5
>
> commit r13-4861-g8ec5fcb6fc79e5bcca23c3fecbaf09d4566cb1d5
> Author: Arsen ArsenoviÄ <arsen@aarsen.me>
> Date: Thu Dec 22 12:03:06 2022 +0100
>
> libstdc++: Improve output of default contract violation handler [PR107792]
>
> Make the output more readable. Don't output anything unless verbose
> termination is enabled at configure-time.
>
> The testsuite change was almost entirely mechanical. Save for two files
> which had very short matches, these changes were produced by two seds and a
> Perl script, for the more involved cases. The latter will be added in a
> subsequent commit. The former are as follows:
>
> sed -E -i "/dg-output/s/default std::handle_contract_violation called:
> \
> (\S+) (\S+) (\S+(<[A-Za-z0-9, ]*)?>?)\
> /contract violation in function \3 at \1:\2: /" *.C
> sed -i '/dg-output/s/ */ /g'
>
> Whichever files remained failing after the above changes were checked-out,
> re-ran, with output extracted, and ran through dg-out-generator.pl.
>
> Co-Authored-By: Jonathan Wakely <jwakely@redhat.com>
>
> libstdc++-v3/ChangeLog:
>
> PR libstdc++/107792
> PR libstdc++/107778
> * src/experimental/contract.cc (handle_contract_violation): Make
> output more readable.
>
> gcc/testsuite/ChangeLog:
>
> * g++.dg/contracts/contracts-access1.C: Convert to new default
> violation handler.
> * g++.dg/contracts/contracts-assume2.C: Ditto.
> * g++.dg/contracts/contracts-config1.C: Ditto.
> * g++.dg/contracts/contracts-constexpr1.C: Ditto.
> * g++.dg/contracts/contracts-ctor-dtor1.C: Ditto.
> * g++.dg/contracts/contracts-deduced2.C: Ditto.
> * g++.dg/contracts/contracts-friend1.C: Ditto.
> * g++.dg/contracts/contracts-multiline1.C: Ditto.
> * g++.dg/contracts/contracts-post3.C: Ditto.
> * g++.dg/contracts/contracts-pre10.C: Ditto.
> * g++.dg/contracts/contracts-pre2.C: Ditto.
> * g++.dg/contracts/contracts-pre2a2.C: Ditto.
> * g++.dg/contracts/contracts-pre3.C: Ditto.
> * g++.dg/contracts/contracts-pre4.C: Ditto.
> * g++.dg/contracts/contracts-pre5.C: Ditto.
> * g++.dg/contracts/contracts-pre7.C: Ditto.
> * g++.dg/contracts/contracts-pre9.C: Ditto.
> * g++.dg/contracts/contracts-redecl3.C: Ditto.
> * g++.dg/contracts/contracts-redecl4.C: Ditto.
> * g++.dg/contracts/contracts-redecl6.C: Ditto.
> * g++.dg/contracts/contracts-redecl7.C: Ditto.
> * g++.dg/contracts/contracts-tmpl-spec1.C: Ditto.
> * g++.dg/contracts/contracts-tmpl-spec2.C: Ditto.
> * g++.dg/contracts/contracts-tmpl-spec3.C: Ditto.
> * g++.dg/contracts/contracts10.C: Ditto.
> * g++.dg/contracts/contracts14.C: Ditto.
> * g++.dg/contracts/contracts15.C: Ditto.
> * g++.dg/contracts/contracts16.C: Ditto.
> * g++.dg/contracts/contracts17.C: Ditto.
> * g++.dg/contracts/contracts19.C: Ditto.
> * g++.dg/contracts/contracts25.C: Ditto.
> * g++.dg/contracts/contracts3.C: Ditto.
> * g++.dg/contracts/contracts35.C: Ditto.
> * g++.dg/contracts/contracts5.C: Ditto.
> * g++.dg/contracts/contracts7.C: Ditto.
> * g++.dg/contracts/contracts9.C: Ditto.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-23 0:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 6:21 [Bug libstdc++/107778] New: " unlvsur at live dot com
2022-11-21 6:21 ` [Bug libstdc++/107778] " unlvsur at live dot com
2022-11-21 6:24 ` unlvsur at live dot com
2022-11-21 6:28 ` unlvsur at live dot com
2022-11-21 9:58 ` redi at gcc dot gnu.org
2022-11-21 10:01 ` unlvsur at live dot com
2022-11-21 10:01 ` unlvsur at live dot com
2022-11-21 10:01 ` unlvsur at live dot com
2022-11-21 10:17 ` unlvsur at live dot com
2022-12-23 0:51 ` cvs-commit at gcc dot gnu.org
2022-12-23 0:54 ` webrown.cpp at gmail dot com [this message]
2023-02-28 1:25 ` redi at gcc dot gnu.org
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=bug-107778-4-GBlXb455ch@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).