From: Jonathan Wakely <jwakely@redhat.com>
To: Matthias Kretz <m.kretz@gsi.de>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Implement std::unreachable() for C++23 (P0627R6)
Date: Thu, 31 Mar 2022 17:02:07 +0100 [thread overview]
Message-ID: <CACb0b4k2x4PEfXA74kGTdmnC7dbj5CiZ+nXuWnQYf2Q8_Gpgfg@mail.gmail.com> (raw)
In-Reply-To: <3572914.e9J7NaK4W3@minbar>
On Thu, 31 Mar 2022 at 16:51, Matthias Kretz via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> I like it. But I'd like it even more if we could have
>
> #elif defined _UBSAN
> __ubsan_invoke_ub("reached std::unreachable()");
>
> But to my knowledge UBSAN has no hooks for the library like this (yet).
As far as I know, that's correct.
> > +#ifdef _GLIBCXX_DEBUG
> > + std::__glibcxx_assert_fail("<utility>", 0, "std::unreachable()",
> > + "inconceivable!");
>
> Funny message, but it should be more helpful, IMHO. :)
We're currently limited to some string that can go inside "Assertion
'...' failed."
I also considered changing __glibcxx_assert_fail like so:
--- a/libstdc++-v3/src/c++11/debug.cc
+++ b/libstdc++-v3/src/c++11/debug.cc
@@ -55,6 +55,8 @@ namespace std
if (file && function && condition)
fprintf(stderr, "%s:%d: %s: Assertion '%s' failed.\n",
file, line, function, condition);
+ else if (function)
+ fprintf(stderr, "%s called.\n", function);
abort();
}
}
And then making std::unreachable() call __glibcxx_assert_fail(0, 0,
"std::unreachable()", 0).
prev parent reply other threads:[~2022-03-31 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 15:30 Jonathan Wakely
2022-03-31 15:50 ` Matthias Kretz
2022-03-31 15:59 ` Xi Ruoyao
2022-03-31 16:01 ` Marc Glisse
2022-03-31 16:05 ` Jonathan Wakely
2022-03-31 18:21 ` Marc Glisse
2022-04-01 11:33 ` Jonathan Wakely
2022-04-01 11:56 ` Matthias Kretz
2022-04-01 13:01 ` Jonathan Wakely
2022-03-31 16:02 ` 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=CACb0b4k2x4PEfXA74kGTdmnC7dbj5CiZ+nXuWnQYf2Q8_Gpgfg@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=m.kretz@gsi.de \
/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).