public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ldalessandro at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109752] New: [ICE] in check_complete_insertion, at hash-table.h:578 Date: Fri, 05 May 2023 17:50:53 +0000 [thread overview] Message-ID: <bug-109752-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109752 Bug ID: 109752 Summary: [ICE] in check_complete_insertion, at hash-table.h:578 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ldalessandro at gmail dot com Target Milestone: --- The following example is reduced from https://github.com/boostorg/stl_interfaces/blob/boost-1.82.0/example/node_iterator.cpp. It causes the ICE on trunk (gcc-14). #include <boost/stl_interfaces/iterator_interface.hpp> template<typename T> struct iterator : boost::stl_interfaces::iterator_interface<iterator<T>, std::forward_iterator_tag, T> { using base_type = boost::stl_interfaces::iterator_interface<iterator<T>, std::forward_iterator_tag, T>; using base_type::operator++; T& operator*() const; iterator& operator++(); bool operator==(iterator) const; }; static_assert(std::incrementable<iterator<int>>); Live: https://godbolt.org/z/n9hMW4a4b PR: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108451 fails the same assert but I don't know if it's the same cause. PR: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109751 same example may trigger gcc-13 bug (I'm not sure)
next reply other threads:[~2023-05-05 17:50 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-05 17:50 ldalessandro at gmail dot com [this message] 2023-05-05 17:52 ` [Bug c++/109752] " pinskia at gcc dot gnu.org 2023-05-05 17:52 ` pinskia at gcc dot gnu.org 2023-05-05 18:00 ` ldalessandro at gmail dot com 2023-05-05 18:08 ` ldalessandro at gmail dot com 2023-05-05 19:35 ` pinskia at gcc dot gnu.org 2023-05-06 22:08 ` redi at gcc dot gnu.org 2023-05-06 22:10 ` redi at gcc dot gnu.org 2023-05-08 14:40 ` [Bug c++/109752] [13/14 regression] ICE in check_complete_insertion, at hash-table.h:578 since r13-4937 ppalka at gcc dot gnu.org 2023-05-09 19:08 ` cvs-commit at gcc dot gnu.org 2023-05-09 19:10 ` [Bug c++/109752] [13 " ppalka at gcc dot gnu.org 2023-05-12 12:38 ` cvs-commit at gcc dot gnu.org 2023-05-12 12:47 ` ppalka 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-109752-4@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).