public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexander.lelyakin at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99479] [modules] ICE Aborted signal terminated program cc1plus
Date: Tue, 23 Mar 2021 08:48:38 +0000	[thread overview]
Message-ID: <bug-99479-4-bB5ICYkBFK@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 #3 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> ---
in gcc version 20210323:
All three sequences now produce "Segmentation fault" instead of "corrupted
double-linked list".

However the error "corrupted double-linked list" is still reproducible:
----
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header cstdarg
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header source_location
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header locale
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header shared_mutex
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header compare
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header concepts
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header cinttypes
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header numeric
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header string_view
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header iostream
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header variant
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header iosfwd
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header cwchar
/usr/local/bin/g++ -std=c++20 -fmodules-ts -x c++-system-header filesystem
----
corrupted double-linked list
corrupted double-linked list
g++: internal compiler error: Aborted signal terminated program cc1plus
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
----
g++ (GCC) 11.0.1 20210323 (experimental)
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  parent reply	other threads:[~2021-03-23  8:48 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 [this message]
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
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-bB5ICYkBFK@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).