public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/97644] FAIL: gdc.dg/gdc204.d due to ICE in finish_thunk
Date: Fri, 30 Oct 2020 18:56:51 +0000	[thread overview]
Message-ID: <bug-97644-4-ZAHVlRioHi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97644-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Ditto in gdc.dg/pr92216.d:

/ssd/test/src/gcc/97556/gcc/testsuite/gdc.dg/pr92216.d:10:1: internal compiler
error: Segmentation fault
0xe979da crash_signal
        /ssd/test/src/gcc/97556/gcc/toplev.c:330
0x66e57a expand_thunk(cgraph_node*, bool, bool)
        /ssd/test/src/gcc/97556/gcc/symtab-thunks.cc:334
0x9965c8 finish_thunk
        /ssd/test/src/gcc/97556/gcc/d/decl.cc:1708
0x9965c8 make_thunk(FuncDeclaration*, int)
        /ssd/test/src/gcc/97556/gcc/d/decl.cc:1820
0x9b5026 TypeInfoVisitor::layout_base_vtable(ClassDeclaration*,
ClassDeclaration*, unsigned long)

  reply	other threads:[~2020-10-30 18:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 18:55 [Bug d/97644] New: " msebor at gcc dot gnu.org
2020-10-30 18:56 ` msebor at gcc dot gnu.org [this message]
2020-10-30 19:01 ` [Bug d/97644] " msebor at gcc dot gnu.org
2020-10-30 20:13 ` ibuclaw at gdcproject dot org
2020-10-30 20:21 ` ibuclaw at gdcproject dot org
2020-10-30 20:40 ` ibuclaw at gdcproject dot org
2020-11-01  5:39 ` ibuclaw at gdcproject dot org
2020-11-02  9:50 ` ibuclaw at gdcproject dot org
2020-11-02 11:24 ` hubicka at ucw dot cz
2020-11-02 12:18 ` ibuclaw at gdcproject dot org
2020-11-02 12:36 ` hubicka at ucw dot cz
2020-11-07 13:53 ` ibuclaw at gdcproject dot org
2020-11-13 14:05 ` cvs-commit at gcc dot gnu.org
2020-11-13 14:07 ` ibuclaw at gdcproject dot 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-97644-4-ZAHVlRioHi@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).