public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110894] [modules] Program terminates with signal SIGSEGV Date: Thu, 03 Aug 2023 23:06:35 +0000 [thread overview] Message-ID: <bug-110894-4-BW4v6xTQQ5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110894-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110894 --- Comment #3 from Johel Ernesto Guerrero Peña <johelegp at gmail dot com> --- Reduced: <https://cpp2.godbolt.org/z/f3K4WaKnE>. If you comment out the use of `.data()` at the end of `my_string_view.hpp` it works. It originally comes from `<string_view>`'s specialization of `hash`, ` { return std::_Hash_impl::hash(__str.data(), __str.length()); }`.
next prev parent reply other threads:[~2023-08-03 23:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-03 19:29 [Bug c++/110894] New: " johelegp at gmail dot com 2023-08-03 19:41 ` [Bug c++/110894] " johelegp at gmail dot com 2023-08-03 19:50 ` pinskia at gcc dot gnu.org 2023-08-03 23:06 ` johelegp at gmail dot com [this message] 2024-02-16 0:20 ` nshead at gcc dot gnu.org 2024-02-16 0:27 ` nshead 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-110894-4-BW4v6xTQQ5@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: linkBe 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).