public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mmitchel@gcc.gnu.org,
	nobody@gcc.gnu.org, redi@gcc.gnu.org
Subject: Re: c++/10481: [3.3?/3.4 regression] Invalid use of non-static data member causes ICE.
Date: Thu, 24 Apr 2003 13:57:00 -0000	[thread overview]
Message-ID: <20030424135741.13827.qmail@sources.redhat.com> (raw)

Old Synopsis: Invalid use of non-static data member causes ICE.
New Synopsis: [3.3?/3.4 regression] Invalid use of non-static data member causes ICE.

Responsible-Changed-From-To: unassigned->mmitchel
Responsible-Changed-By: bangerth
Responsible-Changed-When: Thu Apr 24 13:57:41 2003
Responsible-Changed-Why:
    I think you worked in this area recently when you fixed this
      type `A' is not a base type for type `B'
    problem.
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Thu Apr 24 13:57:41 2003
State-Changed-Why:
    Confirmed.
    ------------------
    struct A {
        char a;
    };
    
    struct B {
        void f() {
          A::a;
        }
    };
    ---------------------
    
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc
    x.cc: In member function `void B::f()':
    x.cc:7: internal compiler error: Segmentation fault
    
    I can't presently tell whether 3.3 ICEs, since my version
    is a couple of days old. I really should update...
    
    The error happens here:
    (gdb) bt
    #0  finish_non_static_data_member (decl=0x401a0654, 
        qualifying_scope=0x401a03cc) at ../../gcc-3.4-CVS/gcc/cp/semantics.c:1219
    #1  0x080fa827 in cp_parser_postfix_expression (parser=0x401a2f40, 
        address_p=false) at ../../gcc-3.4-CVS/gcc/cp/parser.c:3824
    #2  0x080fb050 in cp_parser_unary_expression (parser=0x401a2f40, 
        address_p=false) at ../../gcc-3.4-CVS/gcc/cp/parser.c:4499
    #3  0x080fb9fc in cp_parser_pm_expression (parser=0x401a2f40)
        at ../../gcc-3.4-CVS/gcc/cp/parser.c:4952
    #4  0x08104c82 in cp_parser_binary_expression (parser=0x401a2f40, 
        token_tree_map=0x8474fc0, fn=0x80fb9e0 <cp_parser_pm_expression>)
        at ../../gcc-3.4-CVS/gcc/cp/parser.c:13571
    
    which is the inner while loop here:
          while (!DERIVED_FROM_P (context_for_name_lookup (decl), access_type))
    	{
    	  access_type = TYPE_CONTEXT (access_type);
    	  while (DECL_P (access_type))
    	    access_type = DECL_CONTEXT (access_type);
    	}
    It ICEs since access_type==0. This code hasn't been
    changed recently, just as the one one frame higher, so
    I can't pinpoint a certain patch.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10481


                 reply	other threads:[~2003-04-24 13:57 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=20030424135741.13827.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mmitchel@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=redi@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).