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: Wed, 06 Apr 2022 07:52:52 +0000	[thread overview]
Message-ID: <bug-100134-4-qbjYQFjLeP@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

--- Comment #4 from Sandipan Mohanty <sandipan.mohanty at gmail dot com> ---
Comment on attachment 52759
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52759
Preprocessed source generated by gcc

This bug remains unhandled as of 6 April 2022, making it difficult to use
modules at all with gcc. The attachment is the preprocessed source generated by
gcc for the minimized example in my previous comment. The ICE continues to
happen when using a freshly compiled gcc after pulling from git on 6 April
2022. git commit id: 9d84ed6812dce4a50e64334e7cc4abdeebe41523

  parent reply	other threads:[~2022-04-06  7:52 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
2022-04-06  7:47 ` sandipan.mohanty at gmail dot com
2022-04-06  7:52 ` sandipan.mohanty at gmail dot com [this message]
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-qbjYQFjLeP@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: link
Be 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).