public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug compile/18202] New: [compile] cv-qualified self-references crash Date: Sun, 05 Apr 2015 13:59:00 -0000 [thread overview] Message-ID: <bug-18202-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=18202 Bug ID: 18202 Summary: [compile] cv-qualified self-references crash Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: compile Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Created attachment 8225 --> https://sourceware.org/bugzilla/attachment.cgi?id=8225&action=edit reproducer for GDB gdb/testsuite/gdb.compile/compile.c struct struct_type { - struct struct_type *selffield; + volatile struct struct_type *selffield; -> compile code struct_object.selffield = &struct_object gdb command line:1:1: internal compiler error: Segmentation fault This is because selffield has !COMPLETE_TYPE_P as at that time struct struct_type is not yet complete and the cv-qualifier creates a copy (not reference) of the type inside GCC. I guess cv-qualified self-references will need to create opaque type inside GCC. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-04-05 13:59 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-05 13:59 jan.kratochvil at redhat dot com [this message] 2015-04-10 12:18 ` [Bug compile/18202] " jan.kratochvil at redhat dot com 2015-05-16 12:43 ` cvs-commit at gcc dot gnu.org 2015-09-20 20:56 ` jan.kratochvil at redhat 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-18202-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).