public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: debug/8384: ICE in is_base_type, at dwarf2out.c:7477
Date: Mon, 28 Oct 2002 11:56:00 -0000	[thread overview]
Message-ID: <20021028195601.5074.qmail@sources.redhat.com> (raw)

The following reply was made to PR debug/8384; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: debug/8384: ICE in is_base_type, at dwarf2out.c:7477
Date: Mon, 28 Oct 2002 13:50:05 -0600 (CST)

 Here's a shorter example:
 --------------------------------
 int foo;
 
 template <class T> struct Base  {
   typedef  T  type;
 };
 
 template<class T>
 struct Derived : public Base<typeof(foo)> {};
 -------------------------------
 
 Message is:
 -------------------------------
 tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -g x.cc
 x.cc: In instantiation of `Base<__typeof (foo)>':
 x.cc:8:   instantiated from here
 x.cc:3: internal compiler error: in is_base_type, at dwarf2out.c:7477
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 -------------------------------
 
 I believe that if this problem is fixed, the code will still not compile 
 but the next issue will then be c++/8385.
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 
 


             reply	other threads:[~2002-10-28 19:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28 11:56 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-28  9:39 bangerth

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=20021028195601.5074.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --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: 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).