public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ioan.mitiu at zimperium dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105631] New: GCC internal compiler error: Segmentation fault when trying to compile Qt 6.3 Date: Tue, 17 May 2022 15:39:04 +0000 [thread overview] Message-ID: <bug-105631-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105631 Bug ID: 105631 Summary: GCC internal compiler error: Segmentation fault when trying to compile Qt 6.3 Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ioan.mitiu at zimperium dot com Target Milestone: --- Got following error when tried to compile sources after a migration from Qt 5.12.12 -> Qt 6.3: ================================================================== /opt/qt/qt-6.3.0/include/QtCore/qfuture_impl.h:137:34: internal compiler error: Segmentation fault 137 | std::is_class_v<class T::QPrivateSignal> | ^~~~~~~~~~~~~~ 0xe4c988 internal_error(char const*, ...) ???:0 0x9ecbcd class_decl_loc_t::add(cp_parser*, unsigned int, tag_types, tree_node*, bool, bool) ???:0 0x14e7873 c_parse_file() ???:0 0x14c9d9e c_common_parse_file() ???:0 ================================================================= In order to reproduce it is needed only to have following includes: #include <QtWidgets> #include <QtConcurrent> together with a member variable like: QFutureWatcher<std::optional<StringVector>> targetsResultWatcher;
next reply other threads:[~2022-05-17 15:39 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-17 15:39 ioan.mitiu at zimperium dot com [this message] 2022-05-17 15:54 ` [Bug c++/105631] " mpolacek at gcc dot gnu.org 2022-05-17 17:34 ` ioan.mitiu at zimperium dot com 2022-05-17 17:52 ` mpolacek at gcc dot gnu.org 2022-10-27 1:08 ` pinskia 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-105631-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).