public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sandipan.mohanty at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100134] [modules] ICE when using a vector in a module Date: Thu, 10 Mar 2022 14:49:35 +0000 [thread overview] Message-ID: <bug-100134-4-rD5uWOd2Ht@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100134-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100134 Sandipan Mohanty <sandipan.mohanty at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sandipan.mohanty at gmail dot com --- Comment #2 from Sandipan Mohanty <sandipan.mohanty at gmail dot com> --- I was about to report something very similar, so I will add my observations to this report: (i) I have reproduced this after pulling and rebuilding today (10 March 2022) from gcc git repository. The commit id for my testing version is 3357878ef56d1e47666fc697cfd7cb5cd9c1dfc9. (ii) The ICE happens even if you don't create a vector instance: // minimal code to reproduce module; import <vector>; export module SomeModule; struct SomeClass { using iterator = std::vector<int>::iterator; }; // end code Compilation steps are as in the original report. In order to avoid possible interference from other header units, I performed each of my tests by first removing gcm.cache/. $ rm -rf gcm.cache $ g++ -std=c++20 -fmodules-ts -xc++-system-header vector $ g++ -std=c++20 -fmodules-ts -c module_ICE_1.cc -freport-bug (iii) One can change vector to deque, list, forward_list or a set, and still have the same error. Changing the container to std::array does not cause this specific ICE. (iv) Replacing the container with std::map<int, int> still has the same error, but std::unordered_map<int, int> does not! With an unordered_set, one can get further and create objects in the module.
next prev parent reply other threads:[~2022-03-10 14:49 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-18 9:48 [Bug c++/100134] New: ICE when using a vector in a mdoule patrick.kox at commandoregel dot be 2021-06-20 9:03 ` [Bug c++/100134] [modules] ICE when using a vector in a module ensadc at mailnesia dot com 2022-03-10 14:49 ` sandipan.mohanty at gmail dot com [this message] 2022-04-06 7:47 ` sandipan.mohanty at gmail dot com 2022-04-06 7:52 ` sandipan.mohanty at gmail dot com 2022-09-26 23:33 ` pinskia at gcc dot gnu.org 2022-09-26 23:34 ` johelegp at gmail dot com 2022-10-07 19:11 ` ppalka at gcc dot gnu.org 2022-10-11 19:03 ` cvs-commit at gcc dot gnu.org 2022-10-12 14:36 ` 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-100134-4-rD5uWOd2Ht@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).