public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live 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: Mon, 21 Nov 2022 10:17:51 +0000	[thread overview]
Message-ID: <bug-107778-4-urA2CdMbN1@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 #8 from cqwrteur <unlvsur at live dot com> ---
(In reply to cqwrteur from comment #6)
> (In reply to Jonathan Wakely from comment #4)
> > (In reply to cqwrteur from comment #3)
> > > Also why the function is not noexcept?
> > 
> > Writing to streams can throw.
> > 
> > If you don't like the default handler you can provide your own.
> 
> The problem is that the function is still not marked as noexcept and it will
> cause serious issues with noexcept functions (like using contracts in
> operator[] for example)

btw I do not know whether there is a toggle to just add a contract check with
__builtin_trap() or std::terminate for example. The current implementation of
the contract ts in GCC is ridiculously expensive tbh due to too many parameters
that need to be passed into the handler function.

  parent reply	other threads:[~2022-11-21 10:17 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 [this message]
2022-12-23  0:51 ` cvs-commit at gcc dot gnu.org
2022-12-23  0:54 ` webrown.cpp at gmail dot com
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-urA2CdMbN1@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).