public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99479] [modules] ICE Aborted signal terminated program cc1plus
Date: Mon, 24 Jan 2022 17:56:57 +0000	[thread overview]
Message-ID: <bug-99479-4-vX3WeEqvIK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99479-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99479

--- Comment #21 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Patrick Palka from comment #20)
> Using a non-static vector fixes the valgrind error.  Is this a fix that's
> worth applying at this point?

I do think it might fix a bunch of modules issues where the ICE can come and
go. Maybe when GCC 12 branches off, we remove the static but keep this bug
report open and see if there is a way to fix this for GCC 13? The number of
ICEs reported against modules keep on growing as more people are using it and
getting rid of the biggest memory corruption issue will at least allow more
people to test out modules in my mind.

  parent reply	other threads:[~2022-01-24 17:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09  7:37 [Bug c++/99479] New: " alexander.lelyakin at googlemail dot com
2021-03-11  8:16 ` [Bug c++/99479] " alexander.lelyakin at googlemail dot com
2021-03-12 10:18 ` alexander.lelyakin at googlemail dot com
2021-03-23  8:48 ` alexander.lelyakin at googlemail dot com
2021-03-23 20:11 ` alexander.lelyakin at googlemail dot com
2021-03-24 19:44 ` alexander.lelyakin at googlemail dot com
2021-03-27  6:44 ` alexander.lelyakin at googlemail dot com
2021-03-30  1:25 ` mpolacek at gcc dot gnu.org
2021-03-30  6:43 ` alexander.lelyakin at googlemail dot com
2021-04-16 18:51 ` alexander.lelyakin at googlemail dot com
2021-04-16 18:53 ` alexander.lelyakin at googlemail dot com
2021-12-30 16:09 ` pinskia at gcc dot gnu.org
2021-12-30 16:10 ` pinskia at gcc dot gnu.org
2021-12-30 16:11 ` pinskia at gcc dot gnu.org
2021-12-30 16:12 ` pinskia at gcc dot gnu.org
2021-12-30 16:12 ` pinskia at gcc dot gnu.org
2021-12-30 16:12 ` pinskia at gcc dot gnu.org
2021-12-30 21:34 ` pinskia at gcc dot gnu.org
2021-12-31  4:13 ` pinskia at gcc dot gnu.org
2021-12-31  4:20 ` pinskia at gcc dot gnu.org
2022-01-01  4:09 ` pinskia at gcc dot gnu.org
2022-01-24 15:52 ` ppalka at gcc dot gnu.org
2022-01-24 17:56 ` pinskia at gcc dot gnu.org [this message]
2022-04-07 20:10 ` cvs-commit at gcc dot gnu.org
2022-10-20 12:57 ` LpSolit at gmail dot com

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-99479-4-vX3WeEqvIK@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).