public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "porten at kde dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114795] internal compiler error: in finish_member_declaration after module import in gcc 14.0.1 snapshot Date: Mon, 22 Apr 2024 07:37:44 +0000 [thread overview] Message-ID: <bug-114795-4-aibr3cWBNb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114795-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114795 --- Comment #4 from porten at kde dot org --- Thanks for the reminder about the workaround. I had once seen it before trying module but did not see the relation when running into problems later. In the small test case, reordering the import and includes helps! It is just that the original code base exposes another problem. In fact, the original one I experienced: /opt/gcc-14/include/c++/14.0.1/format: In member function ‘auto std::__format::_Sink_iter<_CharT>::_M_reserve(std::size_t) const [with _CharT = char]’: /opt/gcc-14/include/c++/14.0.1/format:2632:7: error: invalid conversion in return statement 2632 | _M_reserve(size_t __n) const | ^~~~~~~~~~ <<< Unknown tree: template_type_parm >>> struct _Reservation return D.267932; /opt/gcc-14/include/c++/14.0.1/format:2632:7: internal compiler error: ‘verify_gimple’ failed 0x138b51e verify_gimple_in_seq(gimple*, bool) /home/porten/git/gcc/gcc/tree-cfg.cc:5318 [...] If of any interest, I can try to reduce a test case preserving the error.
next prev parent reply other threads:[~2024-04-22 7:37 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-21 14:38 [Bug c++/114795] New: " porten at kde dot org 2024-04-21 22:17 ` [Bug c++/114795] " porten at kde dot org 2024-04-22 0:20 ` porten at kde dot org 2024-04-22 1:52 ` nshead at gcc dot gnu.org 2024-04-22 7:37 ` porten at kde dot org [this message] 2024-04-22 8:51 ` nshead at gcc dot gnu.org 2024-04-22 22:49 ` porten at kde dot org 2024-04-23 16:14 ` ppalka at gcc dot gnu.org 2024-04-23 18:01 ` cvs-commit at gcc dot gnu.org 2024-04-23 18:09 ` ppalka at gcc dot gnu.org 2024-04-24 7:15 ` porten at kde dot 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-114795-4-aibr3cWBNb@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).