public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: giovannibajo@libero.it To: Shea.Williams@colorado.edu, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/10635: ICE (segfault) when dereferencing an incomplete type casted from a void pointer Date: Tue, 06 May 2003 10:43:00 -0000 [thread overview] Message-ID: <20030506104357.15624.qmail@sources.redhat.com> (raw) Old Synopsis: g++ seg faluts on compile command New Synopsis: ICE (segfault) when dereferencing an incomplete type casted from a void pointer State-Changed-From-To: open->analyzed State-Changed-By: bajo State-Changed-When: Tue May 6 10:43:57 2003 State-Changed-Why: Confirmed, it ICEs 3.3 CVS 20030503 and 3.4 CVS 20030503. ------------------------------------------------------ struct INCOMPLETE; void* foo(void); struct Foo { void get_incomplete(INCOMPLETE ); void bar(void) { get_incomplete((INCOMPLETE) *((INCOMPLETE*)foo())); } }; ------------------------------------------------------ pr10635.cpp: In member function `void Foo::bar()': pr10635.cpp:11: internal compiler error: Segmentation fault The code is illegal because it is trying to use an incomplete type (in the original code: QDateTime was not yet defined when TimeLabel::qt_invoke() is compiled, probably it's just a matter of including one more header). Not a regression: 2.95 had an accept-illegal on this, so it's slightly better now, the code is rejected (even if not gracefully). http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10635
reply other threads:[~2003-05-06 10:43 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030506104357.15624.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --cc=Shea.Williams@colorado.edu \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: 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).